Distinguish between "workview" filtering and "actionable" tasks about gtg HOT 6 OPEN

Two things bother me about the actionable tab:

1. It shows all tasks that aren't due in the future. Since I do daily/weekly planning, that means 99% of my tasks in open will also be in actionable unless I set them all to "someday"
2. You are forced to set some due date to get tasks to show at the top. Otherwise they are lost in the sea of tasks, since you can't sort by start date.

It feels like it should act as "focus" filter so you only see what you are set to do next, but it ends up being a mess because the algo has so many conditions that you never know when/if a task will show up there.

Once the core rewrite is done we could move the tabs to the sidebar and open the possibility for plugins to create their own views too.

from gtg.

Another potential approach to this would be for workview and actionable to be two independent view "filters" that the user can toggle in the UI on the fly, instead of view "modes". But one has to be careful not to bury the reachability of those toggles too far, nor to clutter the UI, so it might be a tricky thing to achieve.

from gtg.

...and it should probably be revisited once we have solved the performance problems after a switch to lxml and such, because if switching between view modes is much faster in 0.5 than in 0.3.x, then this might make the "in-between all-tasks and workview" state less important to have.

from gtg.

@diegogangl See also #429

from gtg.

Possibly the "Actionable" view (or "Workview" as it was previously called) tab approach is a mistake of oversimplification, and we should instead offer a filtering bar with independent toggles the user could use. So you'd only have the distinction between Open/Closed, and then, in some sub-toolbar somewhere (maybe toggleable with a "Filters" button in the headerbar?), have GtkSwitch widgets (?) controlling these:

• "Next Actions" only (this would toggle between the hierarchical vs flat view of only-the-last-children)
• Deferred tasks (this would show/hide any tasks—and their children—whose start dates are in the future)
• "Someday" tasks
• Non-workview tags' tasks

This might significantly complicate the UI visually. I wonder if this would be considered plugin material at that point...

from gtg.

Or, perhaps it's really just a matter of having one or two more global view modes, so in total, we could have:

The tricky thing is that in theory, one might consider that "actionable" and "workview" really are independent, not-mutually-exclusive things, that my table above doesn't truly allow, still. So here's another crazy idea: what if workview was really something purely about tags, and was controlled from the tags sidebar, so that in the sidebar you'd have a set of switcher buttons between "All tags" and "Workview", which would independently affect which tags get shown (and thus which tasks get shown, too) in conjunction with the global view modes which would become:

*: in both cases, the trickiest view mode to define—if it's pertinent to have it at all—is the "Review" mode... because possibly everyone has a different definition of what they would like to review. However:

• Maybe the review mode could be the "cheat mode", i.e. it's like the "Open" mode BUT it toggles open the custom filtering bar with all the GtkSwitch togglebuttons that the user can independently flip on/off. So in a way, you'd still have a default UI that offers the simplicity of the actions-vs-projects view modes, AND a fully customizeable review mode for those who seek to drill down with full flexibility.
• Maybe the "Review" view mode could be shipped as a plugin to reduce potential UI confusion for users who are getting started.

from gtg.