Nicely written article. However, the pre-processors seem like a great way of extending existing framework code. I'm thinking Bootswatch (with Less).
BTW, he uses some great quotes. Love this one ... * “Everyone knows that debugging is twice as hard as writing a program in the first place. So if you’re as clever as you can be when you write it, how will you ever debug it?”* Right! :) On Friday, October 5, 2012 12:50:24 AM UTC+1, Paolo Caruccio wrote: > > I completely agree with everything Niphlod said in his message. > Based on my experience, the css file is only a dress for a pre-existing > structure in html. > Not surprisingly, Niphlod mentioned "zengarden", namely a html template > having css selectors already set, to be dressed. > In fact, the CSS frameworks, at least that I know, are always accompanied > by a html template. > For this reason, I think is not simple to fit a css file from framework B > to the html template from framework A or to my template without adapting it > before. > In some cases the pre-processors are very useful to speed up coding, but > there are argumentations against them (for example > http://blog.millermedeiros.com/the-problem-with-css-pre-processors/). > > Il giorno giovedì 4 ottobre 2012 00:20:44 UTC+2, Richard ha scritto: >> >> Hello, >> >> I am not exactly sure how this is relevant about how web2py approach to >> bootstrap, but it seems to be a logical evolution of the decoupling content >> and container with HTML/CSS/PHP,Python, etc., as exposed in the post. >> >> >> http://ruby.bvision.com/blog/please-stop-embedding-bootstrap-classes-in-your-html >> >> Happy reading. >> >> Richard >> > --
