On Jun 13, 2005, at 2:42 AM, Mikhail Bozgounov wrote:
The proposed options:
> A) lowercase: #mainnav, #subnav, .bannersmall, .firstpara
> B) lowerCase: #mainNav, #subNav, .bannerSmall, .firstPara
> C) lower-case: #main-nav, #sub-nav, .banner-small, .first-para
> D) lower_case: #main_nav, #sub_nav, .banner_small, .first_para
Most of you support options A) & B), but since
thisstylenamingconvention is not as readable as
thisStyleNamingConvention, option *B)* appears to be most acceptable
and bulletproof.
Note: id and class names are case sensitive in XHTML, even when served
as text/html. Therefore if you use camel casing and choose words that
may be compounded or not, you may get odd results:
#topNavBar { ... }
<div id="topNavbar"> ... </div>
That style will not get applied, and can be the source of frustration
for some hapless coder. This is especially true for teams of coders,
who may not read the same "words" and so may capitalize differently.
I still camel case, because readability is a constant concern, and
where the words are is something people only need to learn once.
Choosing short, clear names goes a long way.
--
Ben Curtis : webwright
bivia : a personal web studio
http://www.bivia.com
v: (818) 507-6613
______________________________________________________________________
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
