-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A better/faster task deferring feature #244
Comments
The goal of "not today" is really to be a simple, one clic action. The goal is to clean your task list so you can end your day with an empty task list. Anything that requires a choice would completely defeat the purpose of the feature, IMHO. |
Ah, I think I introduced some confusion with the issue title there... my idea here is to extend the general "Set Start Date" contextual menu feature, not replace the simplicity of the "Not today" button. Though there's also the question of what happens of the "Not today" button in a world of headerbars, but that's not what I was trying to look at here ;) |
I haven't really used the old plugin, but I've wanting a way to reschedule tasks more easily for a while. Right now I can select some tasks, right-click and change the due date to tomorrow but if I wanted to defer them to say, the end of the week I would need to go task-by-task. I don't think requiring an extra click is a bad trade if we get something more powerful. Here's another idea, we add a button in the headerbar (at least for now). That button opens a popup menu with submenus/sections like this:
|
I have this done in the Here's a demo: |
This looks like a great improvement already, I'm looking forward to using it! There's the theoretical question of if the "pick custom date" widget set could be embedded directly in the popover (maybe with a two-columns Grid) to "save one click" I guess, but that might be crowding that UI and complexifying the implementation and I'm not sure how it would work for Accessibility either so... yeah, I think your current implementation is already good for 99.9% of cases ;) Some suggestions:
I also thought of some more things now:
|
I wanted to do that but I couldn't figure out how to do sub-menus in popups and just went ahead with something easier. We could include it as an improvement for 0.5
Good point, done!
They had tooltips, except the start tomorrow button (cause I forgot). Fixed too.
I thought it would look weird to have the sequence of days with one of them missing. But I think I found a nicer solution with separators
You can still use it when sorting by start date in the open pane. I think we should have it for completeness sake, and it might be useful when we add more powerful filtering/sorting later |
Gave it a shot tonight, some UI remarks:
|
The best place would probably be a popup that comes from the rows, or subtoolbar like you are suggesting. But before we do any of those we need to move to listboxes. That's why I added it in the headerbar. I've also added the start date options to the context menu but I haven't been able to change the labels to reflect the days of the week. Apparently you can't modify a GtkMenuModel and all the menus are coming from .ui files. Another thing to fix once we get to listboxes. |
Closing since we will tackle this when we move to listboxes |
In 0.3.x, GTG had a "Not today" plugin, that we're supposed to merge into core GTG (as per #222) for what will become 0.4. It added a button toolbar to one-click change the start date of a task to "tomorrow". More generally, GTG also allowed right-clicking on any task in the main window to "Set Start Date" with one of these values:
Those are reasonably useful, but what I've really wanted all these years is to also have:
...otherwise I have to double-click to open a task, click to focus the Start Date field, pick next Monday, save, etc. It's not really efficient.
Now, of course, we can imagine that a traditional menu with "Today, Tomorrow, Friday, Saturday, Sunday, Monday, Next Thursday, Next month, Next year, Custom" would get kind of ridiculously overloaded. Some potential ways I can imagine solving all this:
Some of those features might already be implemented in the git version, I'm not sure / don't remember... but if they're not, well, this is my user experience wishlist starting point ;)
The text was updated successfully, but these errors were encountered: