> -----Original Message----- > From: Glenn A. McAllister [mailto:[EMAIL PROTECTED]] > > On Thu, 28 Mar 2002, Berin Loritsch wrote: > > > Everything should definitely feel the same. However, color is a > > definite clue that you have changed contexts. By drilling down a > > Project's heirarchy, it helps to have a visual clue that > you are not > > at the same level you used to be. > > > > Color customization is not just a cosmetic tool, it does help to > > understand a project's hierarchy. Logo changes can be > missed, but a > > different background or header color is hard to ignore. > > Unfortunately, you can't depend solely on colour to > communicate an important piece of information. If all > subprojects have a blue background and all subsubproject have > a purple background and thats the only > indication of the project level, anyone who is red-green > colour blind is > hosed. Anyone who is completely colour blind is obviously hosed.
Agreed. That is why the the the logo changes as well. The color change is just an additional cue to the non-colorblind. > I don't disagree that colour is a very useful tool, just > don't depend on it. You need an additional way of indicating > what the current project depth is. > > And no, I'm not colour blind. :-) Contrast is just as important. A better analogy would be if we alternated light and dark. Now, if the light color was lt. red or yellow, it doesn't really matter to the colorblind. The next level down would become dark again. But that choice should be left to the sub projects to decide their color schemes. It is an easy change to support, and it communicates enough information without becoming a crutch. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
