Mimi Yin wrote:
Can I ask what you use the Dashboard collection for? Is it your
primary 'view'? the place you sit in most of the time when you're
using Chandler?
I use it almost never at all. I mostly switch between the calendar, in
which I usually have overlaid all collections that have events (Home,
Work, and Errands, with Errands hardly having any since they're mostly
tasks and I only stamp them as events when they have a specific
deadline), and the task list for the collection corresponding to the
context I'm currently in (i.e., Work vs. Home vs. running Errands). I
appreciate the original goal to using the Dashboard to give one a GTD
'runway' view, but at least in alpha4 it doesn't really do it. Seeing
all my collections at once doesn't give me an overview, but an
overwhelming view. :-)
I had a look at the Wiki page and I like your proposal. I think it would
go a long way toward making the Dashboard an important part of my
workflow in Chandler. The way I see it, it would allow me to use the
Dashboard primarily as my "Inbox", to check and process new information,
something that I can't easily do in the current version. (I should add
that I don't connect Chandler to my mail account and use it without
sharing any information with others, so I am the only creator of all
items and keeping track of new information using the existing features
is not as difficult as when multiple people get involved.)
I'm still not sure how you envision a scenario to use the Dashboard to
"once a day or once a week review their areas of responsibility and tidy
up their project plans", though. (The third bullet in the "design that
accommodates different work styles" section.)
Davor
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
