You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
dreeves opened this issue
Aug 20, 2018
· 2 comments
Assignees
Labels
ADOConsensus needed on what to Actually Do (or "much ado about ∅"), AKA questionRFERequest For Enhancement AKA feature requestSTYStyle/polish/CSS, or think of it as in pigsty or an eyesoreUVIUser-Visible Improvement
[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.
The text was updated successfully, but these errors were encountered:
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
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.
ADOConsensus needed on what to Actually Do (or "much ado about ∅"), AKA questionRFERequest For Enhancement AKA feature requestSTYStyle/polish/CSS, or think of it as in pigsty or an eyesoreUVIUser-Visible Improvement
Here's an off-the-cuff proposal -- help with filling in actual hex codes solicited!
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.
The text was updated successfully, but these errors were encountered: