Unless you need to generate CSS dynamically based on the request, I would think it would be more efficient to compile the CSS once and serve it from 'static' -- that would avoid repetitive computation and allow for browser caching, no? It's also more portable that way. Anthony
On Monday, June 27, 2011 7:23:58 AM UTC-4, mcm wrote: > Wouldn't it be nice to manage the lesscss variables (they look much > like macros) from inside web2py? > That would add just a tiny computational effort on the server. > > mic > > 2011/6/27 Massimo Di Pierro <massimo....@gmail.com>: > > I agree. Moreover when we move stuff like this to the client our apps > > get faster, when we move it to the server they get slower. > > > > On Jun 26, 10:55 pm, Joe Barnhart <joe.ba...@gmail.com> wrote: > >> I guess we could roll our own. But I see it more like jQuery and > >> other add-ins. Life would be very difficult if we tried to duplicate > >> _everything_ in Python! > >> > >> This looks easy to use, it's pretty small, and sort of... well... > >> "elegant" for lack of a better word. It is aesthetically pleasing as > >> well as useful. > >> > >> I just thought others may like to know about it... > >> > >> -- Joe > >> > >> On Jun 27, 4:16 am, Jason Brower <enco...@gmail.com> wrote: > >> > >> > >> > >> > >> > >> > >> > >> > As nice and easy as it is (I love how easy the language is). Couldn't > >> > we just do this with python? That way we could just add our css file > as > >> > a dynamic file like the others. > >
