On 12 Apr 2007, at 18:19, [EMAIL PROTECTED] wrote: > Why must all todos have a context associated with them?
> How do people using tracks deal with actions that you've entered on > a project, > but don't want to see them yet in your context list on the homepage? I don't think that the context is the issue: you want either: a) Some way of marking the 'next actions' in a project, or b) Action dependencies within projects a) is possible in a roundabout way in the trunk by using tags (tag your project next actions as 'next-action' or whatever, and you can view those on their own page), but b) is not yet done. We've talked about it and will probably implement it at some point. > What's the sanctioned > way of dealing with this problem? BSAG and Luke, how do you guys > work your > system. Am I the only one running into this? I'm sure you're not the only one running into it, but for myself, I really don't find it to be a problem, but then my needs are simple, and my projects are fairly odd (never-ending or recurring, and actions tend to get gradually added as they come up). > My interpretation of GTD > is that during my reviews I would move tasks from my project to my > contexts > when they become actionable, but that I could still keep track of > tasks that > have dependencies in terms of my projects. I'm not sure that's how I see it: I think that every action needs a context [in which it can/should be done]. The issue of whether you show *all* actions on the home page is a separate issue. cheers, bsag -- but she's a girl - the weblog of a female geek http://www.rousette.org.uk [EMAIL PROTECTED] _______________________________________________ Tracks-discuss mailing list [EMAIL PROTECTED] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
