[Design] [Cosmo] Login-related workflows update

[Mimi Yin]

Hi Matthew, see comments in-line...

On Nov 17, 2006, at 11:49 AM, Matthew Eernisse wrote:

> It doesn't seem to make much sense to me either to put the link to  
> the browser in account settings. Putting those two together is  
> blurring the line between 'prefs/settings' and 'content I have on  
> the server.' 'Content on the server' is the same stuff whether you  
> look at it in the collection browser, or in the normal UI view.

I'm glad you articulated this point because I think this is precisely  
where we're having a mismatch in mental model. I'm going to follow-up  
with a separate email on this point, but I had a few questions about  
the stuff below I wanted to ask first :o)

>
> If we're going to be implementing actual dropdown menus anyway, why  
> would we not put the link to the home collection browser in one of  
> the menus, like you would with a normal app? That might make more  
> sense than blurring together conceptually unrelated items for a  
> sort of short-term convenience.

By dropdown menus, do you mean the File/Edit menus? I wasn't aware  
that we were doing that.

>
> This also applies to the idea of asking people to choose which UI  
> they want before they log in seems kind of clunky and unnecessarily  
> complicated. Why not just add/remove items in a drop-down menu?

I think I'm not following 'add/remove' items in a drop-down menu.  
Could you elaborate on that more? By items, do you mean shared  
collections? Or do you mean, add and remove views from view selector  
widget.

Mimi