-
Notifications
You must be signed in to change notification settings - Fork 121
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
UI: a better priority picker mockup #410
Comments
Can you assign me this issue?? |
@arjav1528 just curious, how's that coming along? |
@Pavel401 I've opened a PR for this problem; please review it whenever it's convenient for you and merge it into the main branch. |
That looks great!.. but how about reversing the order, or better yet, L-X-M-H like the layout in #410? and does your code set the default option? If so, IMHO, that should default to X. Thanks! |
@linuxcaffe I have reversed the order as mentioned in the mockup, but recorded the screen before pushing the last commit ;)) |
you can check as well in the PR and about the defauly option, yep, I have set it to the X |
@arjav1528 awesome! |
@Pavel401 @linuxcaffe could you please merge the PR?? |
Describe your improvement idea or feature request
Here's an idea for a cleaner, clearer, quicker priority-picker dialog. It's better because
a) one tap to change priority
b) the dialog shows the available options, the order in which that will have an effect*, and the color cues used to represent them.
note: clever taskwarrior users have, in the past, pointed out that of a user actually assigns a "L" priority, that should be almost always be considered lower than NO priority assigned, so the order indicated in the mockup should be the order applied to the urgency coefficient.
On that note, imho, no priority assigned ( X ) should be the default, unless otherwise selected by user.
How would you like to see it implemented?
use something like this mockup in new task and edit task dialogs
Put here any screenshots or videos (optional)
How can we contact you (optional)
No response
Would you like to work on this issue?
None
By submitting this issue, I have confirmed that:
The text was updated successfully, but these errors were encountered: