> What would sort of make sense would be classes
like "wrong", "no" or
> "decrease", which would all have the same red color, but would mean
> different things. But now we're heading for unnecessary obstacles to
> editors...
Yes. Agreed. I just picked an arbitrary class name
here. The only point I
was trying to make is moving inline styles to a class gives us more
consistency. If the color red means 'wrong' we should call the class
wrong. I wasn't for one minute suggesting we should introduce classes
for every specific color.. that would just be stupid :P
I like the idea of class names for different things, and I don't think that
it would unduly burden the editor. As they are already using inline styles,
I think that using classes shouldn't be an undue burden. It is no harder to
say class="someClass" than it is to say style="color: #123456", in
fact, I
would argue it is easier.
Thank you,
Derric Atzrott
Computer Specialist
Alizee Pathology