Ok, I think I understand now the reason behind the design decision, but when I am done with all actions in a context, I often like to see what's up next. I do think dependencies would lessen the need for this.
What is your opinion about adding a collapsed-by-default "Deferred" section in the context view? Do you think it would clutter the UI too much? Or are there more cons with this approach? BR /Henrik On Thu, May 14, 2009 at 8:11 PM, <[email protected]> wrote: > On 14 May 2009, at 17:55, Henrik Bohre wrote: > >> yes, that's correct. But why treat the context view with less respect? :-) >> >> I just don't see that it should be very difficult to implement, so >> therefore I wonder if it is a design decision that someone made, for >> reasons that are not obvious to me. >> >> Or is people not using the context views as much as I do? > > I think that most people use the context view to _work from_ (i.e. to check > what they need to do next), while the project view is used for _planning_. > So in that respect, it makes more sense for you to be able to see your > deferred actions while you're planning, but not in context view. After all, > the whole point of deferring an action is to get it out of your face because > you can't actually do it now. > > 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
