> Having a projects navigator is necessary. Well, having good navigator. But > what is good navigator? What should such navigator contain and provide?
I'm wondering why we even need a project navigator... ? I envisioned the first view of my mockup < http://www.jesseross.com/clients/etoile/ui/project_based/01/ > as the method of managing projects. Maybe we can add badges and a menu to enable certain functionality (like sharing a project between users, or locking a project so editing is not possible), but I don't think something like a glorified file manager is a good idea -- that would make users learn two methods of navigating files (file manager and spatial/desktop). Another part of what I like about the mockup is you don't need to name a project -- its icon (which is just a miniaturized version of the desktop) is its identifier. Having a navigator might undermine that advantage. > Btw. considering the virtual desktops - it is a very thin ice, as many > users may fall into everything-in-one desktop usage. therefore, what shuold the > project manager provide so the users will use it and will not go to the > single-desktop/single-project usage? Like Nicolas said, using Projects should enhance the experience for people who want to use them. Those who don't won't be impacted (just like the use of Expose in OS X -- if you like it, you use it, if you don't, it doesn't impact your pre-established workflow). J.
