> I don't think the Collections menu is as disconnected as the Share menu, > so I don't like putting in the Collections menu into the sidebar. >
Personally, I am not super attached to getting rid of the collections menu, though it does make sense for many of the things in it, like delete, to be doable by clicking on or by the collection itself. I am generally not a big fan of having the same control in multiple surface level places (command keys and shift clicks dont count). The truth is there are only a few things in the collections menu that are global (like "new") so it seemed odd to have those items sitting, lonely, in the menubar menu. That said it is not horrible. But if you have things like "delete" in a menubar level menu, then you get back to the issue of needing to be aware of what the "current collection" is which is more brainpower than I think is really required. > Selecting all collections is not the same as the Dashboard. Dashboard is > the special collection that contains all the important stuff to you. Actually, to quote from the item you linked me to: "The Dashboard is the runway view of all of your information. The closest thing users have to a Dashboard today is their email client Inbox." I could not find any reference to the idea of importance. In fact the design document spends many paragraphs discussing the benefits of the dashboard workflow as compared to using email. But if "importance" is indeed key, it is not obvious in the software design. Again, the problem is that in the current design one of the key features to using this is deciding to "leave this item out of the dashboard", which is very unintuitive. I guess I don't understand why dashboard can't be just another collection. If you want to have the concept of a default collection (which is what dashboard *really* is right now) then that could perhaps fix this. There is nothing about the way that the dashboard works now that says "important". In fact, if that is the intent perhaps it would best be called "important". But then having everything default to being called "important" would, I think you could agree, be weird. As far as I am concerned, "show all" gives me all the benefits of the dashboard, and most importantly it is easy to understand. I think whatever subtle benefits are intended with "dashboard" over a "show all", those benefits are by far trumped by the *critical* need for understandability. Hank _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
