[documentation] Request: Drupal Stylesheet Guidelines
Christian Berg
xeniac at gmx.at
Tue Jul 11 14:24:52 UTC 2006
> The case convention gets to be interesting because there's already such
> a variety in module names. Perhaps consistency with module names isn't
> a necessary goal, but my preference would be to preserve case at least
> for those modules using CamelCase. I'm also not sure if there needs to
> be a convention to distinguish between classes defined by modules and
> those defined by themes, or between classes and ids. (I'm constantly
> using . when I should use #.)
XHTML is case sensitive, for this reason i think we should stick to a
lowercase naming.
For example you would like to theme CamelCase:
div.CamelCase != div.camelcase
When you look at drupal.css and many other modules you will see that
many/all of them are using lowercase classes an id's.
So somebody without a solid CSS knowledge would use .camelcase instead
of .CamelCase an starting to file Bugreports.
IMHO a simple and clear naming has more pros than cons look at PHP:
is ist var_dump() or vardump()? is it gettype() or get_type()?
lowercase with '-' instead of '_' makes the best sense for me.
so we had #camelcase #image-import #og-gmap, #audioblog
greetings
Christian
Wußten Sie schon... ... daß auch Zwerge klein angefangen haben?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 4868 bytes
Desc: not available
Url : http://lists.drupal.org/pipermail/documentation/attachments/20060711/ce5b54ae/smime.bin
More information about the documentation
mailing list