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 --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
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 > > >--~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
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 <thomas-9D208sng4xU@public.gmane.org> 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 rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
skins should generally be completely seperate css files. sure, sometimes skins got basic elements that dont change, these you can put for example into one file "basic.css" and information about colors and so on into the file "autumn.css". On 24 Sep., 16:12, "Jean-Philippe Encausse" <J...-vcK5r0oTKUrk1uMJSBkQmQ@public.gmane.org> wrote:> 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 <tho...-9D208sng4xU@public.gmane.org> 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 rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
Ok and thanks, but what generic class do you use from your automn.css to target all tableS (I don''t know how to explain) visible ? important ? major ? highlighted ... that in this case will be "red" and all visible ? minor ? sided ? that in this case will be yellow ? So is there conventions ? samples ? On 9/24/07, Markus Hammer <yayayay-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > skins should generally be completely seperate css files. > sure, sometimes skins got basic elements that dont change, these you > can put for example into one file "basic.css" and information about > colors and so on into the file "autumn.css". > > On 24 Sep., 16:12, "Jean-Philippe Encausse" <J...-vcK5r0oTKUrk1uMJSBkQmQ@public.gmane.org> wrote: > > 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 <tho...-9D208sng4xU@public.gmane.org> 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 > > > > >-- 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 rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---