[VT-75] VITtk; multiple select

[tbabej]

David Patrick on 2011-04-25T01:04:04Z says:

When performing the same action on multiple tasks, like applying a tag or marking done, it would be very handy to select more than one task at a time. In this mouse-free context, the necessary key-bindings could be something like

toggles _selected_ or _not-selected_. Any previous selection is discarded. The selection then moves down to the next task. to select a block of tasks between the last task selected, and the current task. Any previous selection is discarded. The selection then moves down to the next task. toggles _selected_ or _not-selected_ without losing previous selections. The selection then moves down to the next task. to select a block of tasks between the last task selected, and the current task, without losing previous selections. The selection then moves down to the next task. This could be much faster than performing only one action per selection, refreshing each time.

[tbabej]

Migrated metadata:

Created: 2011-04-25T01:04:04Z
Modified: 2014-02-09T02:23:41Z

[tbabej]

David Patrick on 2011-04-25T01:20:23Z says:

This is really nothing more than the visual method of composing a task ids command, and I think it would be ideal to see that exact formulation in the status area. This reinforces the idea that VITtk is a front-end for task, and things learned in one mode should always be applicable to the others.

[tbabej]

steve rader on 2011-04-25T11:40:45Z says:

David Patrick wrote:

This is really nothing more than the visual method of composing a task ids command, and I think it would be ideal to see that exact formulation in the status area. This reinforces the idea that VITtk is a front-end for task, and things learned in one mode should always be applicable to the others.

This idea is well outside the design scope of VITtk. I never envisioned VITtk being a full blown GUI like application.

[tbabej]

David Patrick on 2011-04-25T14:28:57Z says:

steve rader wrote:

This idea is well outside the design scope of VITtk. I never envisioned VITtk being a full blown GUI like application.

Envisioned or not, considering taskwarriors recently re-rendered roadmap, VITtk is as close to GUI as taskwarriors are likely to see for quite a while. What you whipped up is remarkably like the GUI we imagined years ago, just made of tcl/tk, not c++. For me it's not a cute add-on, but a vital mode that greatly enhances overview, navigation and processing of a sea of tasks, and because of that you'll see me asking for more features and usability.

I don't think I'm in the minority of people who would find this mode ultimately effective, but perhaps I am in the minority of people who can imagine it so.

If VITtk was never imagined to be the full-blown GUI app for taskwarrior, how would you go about making one that was?. From this users perspective, the ultimate GUI would look and act like VITtk +10% enhancement.

[tbabej]

steve rader on 2011-04-25T16:04:54Z says:

If VITtk was never imagined to be the full-blown GUI app for taskwarrior, how would you go about making one that was?. From this users perspective, the ultimate GUI would look and act like VITtk +10% enhancement.

VITtk isn't a GUI--really--there's nothing graphical about it! It's completely character based. I have a vision for a real GUI for Taskwarrior: it would look like Thunderbird except the folder tree would be task data stores and projects, the folder listing would display task listings and the message view would display a single task. There is a very real CHANCE I will code such a thing for Taskwarrior this fall/winter.

Is the "recently re-rendered roadmap" available on-line??

[tbabej]

steve rader on 2012-11-24T18:56:26Z says:

I believe this sorta functionality belongs in Taskhelm, not VITtk nor [[vit|Vit]].