I now have a clearer picture of the Dashboard, and I think my original thoughts are accurate.
The killer for me is the idea of defining something by where it *shouldnt* be. i.e. "keep this out of dashboard". This is very hard to visualize. You want to define where things *should* be, not where they shouldnt be. The way this should work is the way, for example, google calendar works. You have a checkbox next to every collection and so you can show all or just some subset of the collections at the same time. As far as I can tell, the dashboard serves no useful purpose. Hank _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
