> This was done similarly 'back in the day'...
>>http://www.dack.com/web/bullshit.html
fun but not specifically geared towards selecting a n identity for your company
http://www.enormicom.com/index.html
"Take a look at some of the visionary names that
the Nametron 3000 has produced:
Lucent
Scient
Viant
Teligent
Naviant
Noviant
Novient
Aquent
Livent
Omnient
Luminant
Cerent
Agilent
Sapient
Vivant
Ravisent
And many more!
> ... and avoid 'classitis'.
woohoo! way to go, tom, i like the way you think
> For example, if you wanted a particular style in your
> divs with the class of 'foo' to be a certain color:
>> p.foo span { color: #c36; }
no, for DIVs it would be div.foo, not p.foo ;o)
of course spans would never be nested in DIVs, but only in Ps, right?
so you'd probably want to say
div.foo p span { }
but in any case, if you have more than one DIV with a class of foo, isn't that already a form of classitis? or a symptom of some other problem?
a document can have many DIVs, of course, but if you think of the typical structure, there's what, a header, a sidebar, maybe a second sidebar, a main content area, a footer... but where do you get many DIVs that might all have to be treated the same so that they'd all have to have the same class?
like i said, a symptom of some other problem
rudy