[Design] [Cosmo][DF][Sum] Using the Account Browser to restore a lost Chandler repo

[Ted Leung]

What the account browser user may not understand is that they can  
give that URL to someone else to give them access.  It's not a common  
thing in other web apps, and that's why I think it is worth having  
some extra explantion.  Relying on people to read and understand all  
the products and how they fit together is a large assumption.

Ted

On Apr 11, 2007, at 12:04 PM, Mimi Yin wrote:

> Hmmm, aren't Chandler Hub and Chandler Server in the web browser?  
> If we had a URL that took you to a Google Calendar UI, wouldn't we  
> call it Google Calendar? Hopefully the account browser user  
> understands that :) since they're using Chandler Hub / Server in  
> the browser?
>
> On Apr 11, 2007, at 11:31 AM, Ted Leung wrote:
>
>> So if you are doing it by application, then you still need (at  
>> least) one to indicate usage via a web browser.   Anybody with a  
>> web browser, whether they've heard of Chandler *  or not, can use  
>> the PIM url to get access.
>>
>> Ted
>>
>> On Apr 11, 2007, at 9:43 AM, Mimi Yin wrote:
>>
>>> I can see that. So then I would recommend having it by  
>>> application rather than technology, which is also consistent with  
>>> the way we do Subscribe in the end-user UI:
>>>
>>> + Chandler Desktop
>>> + Chandler Hub
>>> + Cosmo or Chandler Server (whatever we end up calling it)
>>>
>>> Mimi
>>>
>>> On Apr 11, 2007, at 9:23 AM, Brian Moseley wrote:
>>>
>>>> On 4/11/07, Mimi Yin <mimi at osafoundation.org> wrote:
>>>>> I understand the current ambiguity around what the word Chandler
>>>>> actually means.  However, moving forward, all of our marketing
>>>>> material will try to beat into people's brains that Chandler =
>>>>> Desktop + Hub + Server... so that we can avoid exactly this  
>>>>> kind of
>>>>> scenario where we end up with a lot of extra copy whenever we  
>>>>> need to
>>>>> refer to things that work for the entire Chandler enchilada.
>>>>
>>>> while "the whole enchilada" is a concept that may work in a large
>>>> sense, when somebody's trying to figure out what's going to happen
>>>> when they click a link or a button, i think we need to be a little
>>>> more explicit.
>>>> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>>>>
>>>> Open Source Applications Foundation "Design" mailing list
>>>> http://lists.osafoundation.org/mailman/listinfo/design
>>>
>>> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>>>
>>> Open Source Applications Foundation "Design" mailing list
>>> http://lists.osafoundation.org/mailman/listinfo/design
>>
>> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>>
>> Open Source Applications Foundation "Design" mailing list
>> http://lists.osafoundation.org/mailman/listinfo/design
>