Re: fanstatic and preprocessors
Jan-Jaap Driessen <[email protected]>
| Newsgroups | gmane.comp.web.zope.devel,gmane.comp.python.wsgi.fanstatic |
|---|---|
| Message-ID | <[email protected]> |
Hi Wolfgang, On 15 April 2011 07:13, Wolfgang Schnerring <[email protected]> wrote: > Hi, > > is this the right place to ask stuff about fanstatic? Fanstatic lives at fanstatic.org , the mailing list at [email protected] . Let's continue this discussion there. > Unfortunately I haven't had the opportunity to have a proper look at > fanstatic (yet!), but I've just been reading about SASS and > CoffeeScript, which are preprocessors/compilers for CSS and > JavaScript. So I wondered whether it is within fanstatic's scope that > one could feasibly write a plugin to support something like this. > Something like, I drop a foo.coffee file somewhere and it would be run > through the CoffeeScript compiler, probably cached, and served to > clients as foo.js. > > (This thought has been triggered by what Rails is doing right now[1] > which is powered by their equivalent resource manager[2].) > > Wolfgang > > > [1] http://www.rubyinside.com/rails-3-1-adopts-coffeescript-jquery-sass-and-controversy-4669.html > [2] https://github.com/sstephenson/sprockets Supporting pre-processed resources is definitely on the fanstatic roadmap. I am working on pluggable support for javascript resources (CoffeeScript, Google Closure Compiler, ...) and CSS (SASS, LessCSS, ...). Cheers, -- Jan-Jaap Driessen _______________________________________________ Zope-Dev maillist - [email protected] https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )