kGTD Development In Light of OmniFocus

It’s taken me a few days to consider what, if any, reaction was warranted by the recent announcement of OmniFocus. Given that I am hopelessly addicted to all the software Omni makes (although I don’t own all of it, I would buy it if I didn’t have a family to feed), I assume I will be migrating to OmniFocus when it ships or enters public beta.

However, I am currently stuck wholly in Kinkless GTD, and I expect to keep working there as well.

So the question comes down to whether I intend to continue to improve/support the many scripts I’ve built to enhance Kinkless GTD.

Basically, I think I’m going to put a halt on my major projects in this regard. Both Mail to KGTD and Send to KGTD Advanced are solid, mature, scripts that run well. I may make some small tweaks here and there, but that’s about it. My plans to build a next-action-summarizer are on hold as are improvements to KGTD to Go (which desperately needs a total overhaul).

As for the many users of these scripts (I think there’s at least three of you out there!), I will continue to squash bugs and provide support as needed, so don’t worry about that.

When OmniFocus ships, I hope to provide the same ease of workflow that my current scripts provide, perhaps even down to the syntax for quick data entry. And, I’ll do what I can to get the Omni folks to put me earlier in the beta so I can get started that much sooner, and maybe have something out on OmniFocus’ drop date.

Twitter, Facebook

Written on October 2, 2006