[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-usability
Subject:    Re: Review Request: --hard_coded_colors in kalarm
From:       Matthew Woehlke <mw_triad () users ! sourceforge ! net>
Date:       2009-08-12 0:56:49
Message-ID: h5t40j$akh$1 () ger ! gmane ! org
[Download RAW message or body]

Matthew Woehlke wrote:
> David Jarvie wrote:
> > Matthew Woehlke wrote:
> > > On 2009-08-11 23:16:35, David Jarvie wrote:
> > > > On 2009-08-12 00:48:33, Matthew Woehlke wrote:
> > > > > http://reviewboard.kde.org/r/1288/
> > > > > 
> > > > > Hard-coded colors are Evil (bad Usability, bad Accessibility,
> > > > > and just plain bad... not to mention not very aesthetic in
> > > > > this case IMO). This removes the major hard-coded colors in
> > > > > KAlarm (default alarm colors, colors in the alarm list), the
> > > > > latter of which are especially bad as they can be illegible
> > > > > in some color schemes.
> > > > 
> > > > This seems a sensible idea. The colours are ok except for the 
> > > > archived alarm colour, which is quite similar in the default KDE
> > > > colour scheme to the disabled alarm colour. They need to be
> > > > clearly distinct by default since disabled and archived status
> > > > are very different.
> > > 
> > > It is? It should be purple (#644A9B) versus gray (#888786).
> > > Semantically speaking, VisitedText is best.
> > > 
> > > If not Visited, what would you use?
> > 
> > I don't really care how the colour is classified, since there isn't
> > one defined as "archived alarm". The important thing is that it's 
> > clearly different from the disabled alarm colour.
> 
> I, however, care about correct semantic use of our color roles (and I also feel \
> that the difference between #644A9B and #888786 is sufficient). 
> As this deals with Usability, anyone else want to comment?

So... I added the usability group because David and I are disagreeing on 
what color role to use for archived. See above.

I also want to add: what weight do we give semantic correctness? 
Alternatively, anyone have a better suggestion what roles to use, that 
wouldn't be bending semantics into a pretzel?

If desired, I can post a screenshot tomorrow.

-- 
Matthew
Please do not quote my e-mail address unobfuscated in message bodies.
-- 
And now back to your regularly scheduled e-mail.

_______________________________________________
kde-usability mailing list
kde-usability@kde.org
https://mail.kde.org/mailman/listinfo/kde-usability


[prev in list] [next in list] [prev in thread] [next in thread]