[chandler-users] using the Dashboard
ax at sonic.net
Wed Feb 13 14:40:24 PST 2008
Rick - I'm brand new to all this and I'd like to rephrase your question
and ask it myself. I know that putting words into other people's mouth
is a killing offense and I don't want to be doing that; So here's my
take on it:
the point of it is that you are to be confused about what buckets you
filed anything into. once you're confused you can dream up schemes to
name your items and because your now spending more time 'planning', get
to request a larger budget for an assistant.
If the tabs related to an item would simply light up when you're on that
item confusion would be lessened; If you would have visual clues on your
items being in multiple buckets/timelines then your confusion would be
lessened. This however would apply downward pressure on your budget,
make your screens easier to understand, and it might mean the end of
relating with that lovely helper.
I've filed several hundred items into chandler over the last 2 weeks and
am doing my best to love this program for all the problems created by
its noob implementors. It a long term gamble on my part actually. I
trust that what I have will work when the money is gone AND that once
that happens a group can take the brilliant guts of it and port this
I'm still only 2 weeks into sorting through an insane amount of tasks
and timelines and love the little dog for what how its brilliantly
effective in my work-flow, but looking at the code, I see the noob
prose, not the marks of folks that can get sh* out the door with ease.
Its a Rock/Hard-Place thing.
Anyway, do pardon my descent into rambling. Perhaps someone else will
pipe-in and enlighten us both about how to properly behold the
awesomeness in front of us.
All the best,
Rick Rawson wrote:
> I suspect that I may be missing an important functionality in
> Chandler: the Dashboard. I have 7 collections and have set each one to
> "Keep out of Dashboard," since I see no utility in seeing my
More information about the chandler-users