Ok Thanks, I'm asking this because I often try to separate structure and content but don't know conventions to use.
For exemple, a Table, visible, with a look n feel or skin should I use: Table.visible Table.colored Table.color Table.dark / Table.ligtht How to explain skin ? Table.red ? Table.automn ? That's complicated :-) On 9/24/07, Thomas Fuchs <[EMAIL PROTECTED]> wrote: > > Not exactly what you asked for, but Rails and some parts of Prototype > and script.aculo.us assume the following conventions: > > For element id's, use (all lowercase): > > blah_blech_blub > > For CSS classnames, use (all lowercase): > > blah-blech-blub > > If you use element ids for numbering, use an integer starting from 1 > as the last part of the element id: > > <div id="comment_1">...</div> > <div id="comment_2">...</div> > > Can't say much about naming conventions as for often-used css > structures (as in your .float class), except that trying to stay away > from "layout-descriptive" classnames is (for most stuff) the best way > to seperate your contents from layout. > > For example, if your ".float" class really means ".picture" or > ".annotation", go for that instead; same thing if your "#column" > element really contains navigation elements, call it "#navigation". > > Of course, special cases (e.g. facebook) might need their own naming > conventions. > > HTH, > Thomas > > Am 24.09.2007 um 15:40 schrieb Jean-Philippe Encausse: > > > > > Hi ! > > I'm sorry if the question is a little bit off topic > > > > Does any body know a serious website that list naming convention for > > css classes/ids ? In a large scope: > > > > - For layout: #Wrapper, #page, #column > > - For look: .colored, .float, > > - For ... > > > > I'm not talking about CSS Framework, the goal behind this is to design > > a generic part of a web site with a kind of css "contract" for other > > developers. > > > > Example ? > > - Login form of application > > - Facebook layouts > > - Generic poll design > > - ... > > > > In Scriptaculous, naming for given widget has been choosen, why or > > why not ? > > > > Regards, > > Jp > > > > -- > > Jean-Philippe Encausse - Veille / R&D Jalios SA > > Jp [at] encausse.net - http://www.encausse.com - http://www.jalias.com > > GTalk: jp.encausse [at] gmail.com - SMS: sms [at] jp.encausse.net > > Mob: +33 6 82 12 56 99 - Job: +33 1 39 23 92 83 - Tel: +33 1 39 18 > > 90 15 > > Do it Once, Use it Twice ~ Do it Twice, Make It Once > > > > > > > > > > -- Jean-Philippe Encausse - Veille / R&D Jalios SA Jp [at] encausse.net - http://www.encausse.com - http://www.jalias.com GTalk: jp.encausse [at] gmail.com - SMS: sms [at] jp.encausse.net Mob: +33 6 82 12 56 99 - Job: +33 1 39 23 92 83 - Tel: +33 1 39 18 90 15 Do it Once, Use it Twice ~ Do it Twice, Make It Once --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
