Quote:
|
Originally Posted by AmberV
A tickler is essentially an item with a "due date" and 0 lead time. It shows up the day it is due. How the user handles it is up to them. They can make a project out of it, actually do it; whatever. So a system built around it is not necessary. All you need is a filter setting that groups by due date (already have a framework for that) to view your "tickler file", and for everyday work, a way to filter out items not due yet (set to Available). Using the Context View, ticklers already exist. :)
|
A "due date" and 0 lead time = start date. Once start and due dates function properly in OF, employing the tickler concept is as simple as assigning a start date to the item. For something many months from now (ie October), set the start date to the first of that month. That's what I've been doing in kGTD and you can put tickler stuff, including events, into this by using a "Remind" context or whatever.
Quote:
|
Originally Posted by AmberV
For some people, offloading time-based things into iCal is okay. Personally, I don't like iCal as a production platform, and I really don't like having to go to two places to see what I need to do. I think timing functions are very integral to project flow, and various timing functions should definitely be integrated into OF.
|
Agreed. Keep it simple. OF for tasks/tickler, iCal for actual hard-coded events (hard landscape). OF just needs robust handling of start and due dates, which I'm sure is being currently developed. I stopped using iCal for To Dos completely after I got comfortable with kGTD and now OF.