GTD Nirvana on Web2.0 ????
I discovered a new Web2.0 (well at least it’s new to me and I can’t find any info about it anywhere but a link on del.ico.us) application today called iOutliner. I may have found the missing link in my GTD implementation. I have been using Backpack as my primary tool for GTD implementation. It works great for context lists of Next Actions (i.e. @Work, @Home, @Computer, @Calls_and_Emails, @Waiting For, etc.). I print my Backpack pages using the mobile layout and setting up Firefox and my printer for 3X5 index cards (works like a charm). I keep all this in a Levenger International Pocket Briefcase which also serves as my wallet and business card holder. This has greatly reduced the amount of stuff that I have to carry around in my pockets. This has been working well except for one minor problem. I have been using Backpack for my Projects list which is ok, but I really wanted a collapsible view so that I could add subprojects and next actions to my projects. Now, of course you can do this sort of by adding a separate page for every Project and then linking from your Projects page to each of those pages, but this is a little cumbersome at best.
Enter iOutliner. iOutliner is an AJAXified Web2.0 application that allows you to create collapsible outlines. I am planning to use it for listing my projects. Hopefully there will be an API and then I will be able to use it in conjunction with Backpack and tie everything together into one package, but for the moment, I intend to continue keeping a Projects list on Backpack and then to use iOutliner for actually managing the projects. I know it will duplicate the projects list somewhat, but this seems like the best solution for me at the moment. I’ll let you know how this works out.
Advertisement

Juset use voo2do for the ultimate web based GTD implementation. You oculd make to do list including projects. It was built around the GTD philosophy.
I looked at voo2do Manny, but it's focus on prioritizing made me feel like it did not really fit the GTD philosophy. I think it was actually built around Joel Splosky's Painless Software Scheduling method.