On 1/29/2011 11:59 PM, Bruno Busco wrote:
Adrian I think we are almost on the same page, please read inline.
2011/1/30 Adrian Crum<[email protected]>
The application developer designs the application, not the graphic artist.
The graphic artist styles the application, he doesn't design it.
100% agreed
For example, I am a developer designing a screen. The screen requires two
sets of links. The links in set A all share something in common, and the
links in set B all share something in common, but sets A and B have nothing
in common. How do I indicate that to the user? I will use different styles
for the two sets of links.
IMO when a developer in this situation he should think: "What is the
functions of the links in set A and i set B?. Are they similar or equivalent
to functions that already exist in the rest of the applications?"
For the set where the answer is yes than the link style should be the one
used for that function in the other application.
For the set where the answer is no than a new style should be defined with a
name that describes the new function.
So, every application that has a group of links that aren't common to
other applications should have its own style for that set of links? Are
you serious? Every application would have its own style sheet then. NO
NO NO. The concept is to have a palette of styles for the application
developer to choose from, not to have a separate set of styles for each
application.
The bottom line is, there is no valid reason to remove the two styles.
There are valid reasons to rename them. If you are REALLY REALLY REALLY
motivated to remove styles, then PLEASE PLEASE PLEASE remove the
deprecated styles - not the ones we're currently using.
-Adrian
