Hi, On Fri, 2009-02-20 at 18:18 +0200, Rimantas Liubertas wrote:
> > The problem > > I've run into is that it's difficult to decide what 'class' a thing > > belongs to until you've got lots of other things to compare it to. So > > what I'm ending up doing in actual practice is to initially use id to > > style elements as the UI emerges, then refactor to classes as the site > > comes together. It's turning out to be a non-trivial exercise. > > Maybe you just lack some practice? Without question. I responded, with what I'd point out was not positioned as a recommendation, because I share the OP's experience having difficulty finding clear, easy-to-follow guidelines WRT 'best practices' that lead naturally to an easily maintained / modified, coherent set of CSS files, Javascript files, and HTML produced by Rails code. Links are always appreciated. Best regards, Bill --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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-talk?hl=en -~----------~----~----~----~------~----~------~--~---
