>>Most of the the rest of us will find the "bright, terrific color scheme" designed by the new programmer gaudy, atrocious, and irritating - just look at what's found on many (ugh) web pages :) Standards have a really good reason, and I'd like to see them spill over into web design a little more, in fact.

If the clients INSIST to make things a little "gaudy", then I think we should be able to without being policed by some standards.


>In general I agree about the standards and good taste in choosing the colors, but I do not agree that the implementation of the standards should restrict the >options for the developer.
>In the real world we have colored buttons and blinking warning lights everywhere. No wonder that the clients ask for them in the applications and are not >happy when you tell them that you cannot have it. If the STOP button in the real world almost always is red, it just does not make sense for the clients. >Standards here should be more of a guidelines or default >settings, then physical restrictions. Why button should be any more different in it's backcolor setting then Label? Just because some group in MS thinks so? If we look at Real Player for example, do we see there Windows standards in the buttons? >And is it a bad design? Isn't using the pictures in the buttons a way to avoid this standard forced to us by MS?

>Nick

Also Nick, I've come accross too many times when a client would want the backcolor of the form to be a certain color or picture. And there are those gray buttons that just don't match the form color. So, I resort to using container object when possible.

In other words, clients sometime really don't care about what the standards are, they just want things to look a specific way.

I know it's just cosmetics, but I'm learning that its a big part of developing a professional class software.