Skip to content
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

Revamp colors for promises based on status and time to deadline #247

Open
dreeves opened this issue Aug 20, 2018 · 2 comments
Open

Revamp colors for promises based on status and time to deadline #247

dreeves opened this issue Aug 20, 2018 · 2 comments
Assignees
Labels
ADO Consensus needed on what to Actually Do (or "much ado about ∅"), AKA question RFE Request For Enhancement AKA feature request STY Style/polish/CSS, or think of it as in pigsty or an eyesore UVI User-Visible Improvement

Comments

@dreeves
Copy link
Contributor

dreeves commented Aug 20, 2018

Here's an off-the-cuff proposal -- help with filling in actual hex codes solicited!

  1. No due date -- obnoxious neon yellow
  2. Overdue -- neon pink [1]
  3. Due in <24h -- bright red
  4. Due in <2d -- orange
  5. Due in <3d -- blue
  6. Due in >=3d -- green
  7. Due in >=7d -- darker green
  8. Completed -- black
  9. Failed (cf Uncle button AKA "mark as failed" #248) -- dark red, almost black
  10. Newly created -- gray [2]

Footnotes

[1] Or show little flames or sirens or something? Blinking would be too much but some kind of subtler animation somehow? Actually the realtime ticking down of the score may be exactly the ticket. And maybe that's the answer for no due date: a blinking "N/A" for the score to goad you into picking a due date to make the godawful blinking stop. :)

[2] This would be moot if we drop create-on-GET but I don't like making the promise gray like in the status quo. Instead, the background of the whole webpage should be a different color or something. Just some unimportant but obvious difference to indicate that the promise has been created.

@dreeves dreeves added RFE Request For Enhancement AKA feature request help wanted ADO Consensus needed on what to Actually Do (or "much ado about ∅"), AKA question STY Style/polish/CSS, or think of it as in pigsty or an eyesore UVI User-Visible Improvement labels Aug 20, 2018
@chrisbutler chrisbutler self-assigned this Aug 21, 2018
@chrisbutler
Copy link
Member

@dreeves i wonder if we should use relative percentages of the time between tini and tdue rather than absolute days... thoughts?

@dreeves
Copy link
Contributor Author

dreeves commented Aug 27, 2018

Smart. I don't think I have strong feeling about this. If it's easy and you think that would be a more helpful color scheme I'm game to try it. But in practice it might turn out that the consistency of like "blue = 2 days" is what's most helpful. I'm imagining a user being all "why is this one green when it's due in a few hours and this one's red when it's due next week?" It could seem buggy unless we think of a way to make it more clear which maybe means some indication of what fraction of the way to the deadline we are, which... is either a good idea regardless or is taking us down a rabbit hole, I'm not sure which...

Vaguely related idea: A table layout where you can sort by any field you want. Default sort could be urgency (status quo) but you could also sort by time to deadline (absolute or relative), promise title, creation date, score, etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ADO Consensus needed on what to Actually Do (or "much ado about ∅"), AKA question RFE Request For Enhancement AKA feature request STY Style/polish/CSS, or think of it as in pigsty or an eyesore UVI User-Visible Improvement
Projects
None yet
Development

No branches or pull requests

2 participants