The Road to Tracks 1.05 from bsag email on Tracks-discuss list

1. Deferred tasks - these are tasks not shown in the main list
because they are deferred because:

a) They are 'tickler' actions which should not be shown until nearer
the time when they are due (e.g. adding an action now to renew your car
insurance, but it's not due until July).

b) They are dependent on the action before it in the project. (e.g. I
can't paint my living room until I've chosen a colour and bought the paints from the shop).

c) They are recurring actions, that I don't need to see until the
recurrence period has elapsed (e.g. pay credit card bill recurs once a month).

2. Getting actions into and out of Tracks via other methods. e.g.
sending an email to Tracks to add a next action automagically, or
getting Tracks to email you automatically every day with a list of
actions due in the next week (though see Luke's tip [2] on using a
cron job and curl to get that ability now). I'd also be interested in
using an XML-RPC backend so that people could code up desktop clients
to interact with Tracks (like Dashboard widgets).

3. Some kind of statistics or reporting on how many actions you've
added or completed and so on. Reading about the Measure Map date
slider [3] gave me all kinds of ideas of ways the data could be
represented and explored.

4. Lots of tidying up and refactoring. I think we could get the
interface to be a lot snappier by a bit of refactoring here and
there. In particular, I'm thinking about making the list of contexts
and projects in the side bar into an overlay that's only loaded when
you roll over or click a link. That way it would only be loaded when
you needed it, and we'd have a lot more page space to play with. In a
similar vein, I'm also thinking about making the home page more of a
'dashboard' with upcoming actions and a summary of the state of
contexts and projects.