CSS/Javascript aren't much of a problem if they hit the whitespace manager within the correct tags -- I forget the name of the processor we were using, but it detected that and didn't alter it. If you use a library built for this task, it's already done. Same thing with 'pre' tags. The problem is when people just strip whitespace.
offloading to gzip was just as fast though, as we still run gzip for the non-whitespace. While we eventually gave up on this for our mako templates, we had to use it on our dust templates - which are rendered both in client and server situations. In order to handle this, we basically created a system where we wrote "source" templates in one directory and a script compiles them into another directory for pyramid (and our javascript build/deploy hook). the source templates are a homebrew bastardization of dust that give us a little more control by writing templates that generate templates. it's crazy in a lot of ways, but it was needed to get around some intricacies. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discuss+unsubscr...@googlegroups.com. To post to this group, send email to pylons-discuss@googlegroups.com. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/d/optout.
