Re: EBN

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: EBN
by Paul Giannaros on Saturday 19/May/2007, @14:28

But hard-coded colours are not always bad. It depends how they are being used, and scripts from EBN would have a hard time inferring that. Hard-coded font sizes/families are less easily justifiable ;-).

Related Links

·   Articles on Usability
·   Also by Paul Giannaros
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: EBN
by Luciano on Sunday 20/May/2007, @01:39

Hardcoded colors are not bad if you do not care for accessibility. Otherwise they are a real problem.

Themes like high-contrast do not work as required if you do not use system colors, for example, in the white-on-black mode, hard-coded black text will not be visible.

Then there is the problem with color blindness, where color blind people may want to adjust colors so that, say warning/OK colors are easy to distinguish.

[ Reply To This | View ]

Re: EBN
by Chani on Sunday 20/May/2007, @06:51

"in the white-on-black mode, hard-coded black text will not be visible."

someone was complaining about exactly this in #kde today. he had a transparent kicker and a black background, iirc, and the text of programs was shown in black when they started up. :)

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"I just wanted to be certain that the code was unmaintainable." -- Charles Samuels
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.