Bug 12919 - Diagnostics addition: colored text to code problems
: Diagnostics addition: colored text to code problems
Status: NEW
Product: SqueezePlay
Classification: Unclassified
Component: --
: unspecified
: PC Other
: -- normal (vote)
: Future
Assigned To: Unassigned bug - please assign me!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-07-17 16:34 UTC by Dan Evans
Modified: 2011-11-06 23:24 UTC (History)
7 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dan Evans 2009-07-17 16:34:20 UTC
Thinking of ways to improve the Diagnostics interface, both for us internally but also for helping customers with issues.

Proposal:

Provide colored feedback to indicate problems creating an at-a-glance UI.  This could either be by coloring the actual text, or by adding a "light" element that is colored.  (the colored light indicators are inspired by Sean and Ben's original diagnostics feedback. see bug 6334.) 

Some examples:

 * WiFi signal strength has dropped below a defined threshold so we display the number in RED.  Or the indicator next the number is now a RED light.

 * Device cannot ping mySqueezebox.com.  Display "Failed" in RED.  Or the indicator light next to it is now a RED light.

Most of the information can be classified into a Green, Yellow or Red state.  Or even just Green and Red.  The exceptions would be the ethernet and wireless connection status *if* that method is unused. (if we're using ethernet, then the WiFi should show RED, but it should show RED if we're using WiFi.)
Comment 1 James Richardson 2009-07-30 10:12:19 UTC
Targeting for next release
Comment 2 Ben Klaas 2009-08-26 07:51:35 UTC
this is an administrative shuffle on priority fields to help make better judgment on the top end of the priority list. P4->P5, P3->P4, and P2->P3.
Comment 3 Chris Owens 2009-10-12 09:42:09 UTC
cc'ing Matt Weldon for his comments
Comment 4 Chris Owens 2009-10-19 09:36:48 UTC
Ben notes we need to be careful of colorblind users with this solution.

Matt notes he needs to talk to Dan about the cases in which this is important.

Dan, since Matt is notoriously busy, you might want to proactively contact him about it.
Comment 5 Chris Owens 2009-10-21 09:49:00 UTC
moving current p2 bugs to p3 to make room for moving p1.5 bugs to p2
Comment 6 James Richardson 2009-10-22 11:38:11 UTC
re-assigning Seth's bugs to Matt
Comment 7 Pat Ransil 2009-10-23 05:11:03 UTC
Administrative move of 7.5 bugs. All P2, P3, P4 being downgraded one level. Will then split P1s.
Comment 8 Pat Ransil 2009-10-23 05:17:10 UTC
Administrative move of 7.5 bugs. All P2, P3, P4 being downgraded one level. Will then split P1s.
Comment 9 Chris Owens 2010-02-02 15:11:13 UTC
Moving Matt Weldon bugs
Comment 10 Alan Young 2011-11-06 23:24:38 UTC
Unassigned bugs cannot have a priority.