The Chandler Project Blog

From a recent post by Lisa Hoover on “Open Source Apps for Homeschoolers”:

Juggling my schedule and that of three young learners — plus all their extra-cirricular activities — isn’t easy. I need to be able to look at a calendar and tell who needs to do what (and who needs to be where) at a glance. To stay organized I use Chandler, an app so feature-rich that I don’t even use it to it’s fullest capability. I love the way it color codes whatever I throw at for easy sorting and retrieval. It also keeps a running to-do list for me, and it’s a snap to create new events, messages, and tasks.

The idea of a “running to-do” list is interesting. To me, it sounds like a task list that is unpredictable, always changing.

When building a task manager, it’s tempting to go down the path of developing features to map out projects with complex task landscapes: dependencies, time estimates, urgency and priority rankings, start times and end times, intermediate milestone dates, etc. There are certainly projects that require this kind of project / task manager (and as an open source project, Chandler can be extended to support such functionality).

However, the kinds of task lists Chandler serves best are precisely “running to-do lists” (or at least my understanding of what a “running to-do list” is.) Task lists that change so quickly, it’s not worthwhile to invest a lot of time inputting and maintaining a lot of meta-data about your tasks. Instead what’s important is a snappy way to get stuff out of your head and onto the task list, plus some basic affordances for tracking (Triage Status + Tickler Alarms) and organizing (Collections + Calendar) your tasks, so they don’t just pile up into one big, insurmountable mountain of to-dos.

This entry was posted on Tuesday, April 15th, 2008 at 2:55 pm and is filed under How I Use Chandler. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.