"I understand that Django has historically been anti-javascript-framework-blessing, and I'm wondering if opening this can of worms would mean having to incorporate some kind of a pluggable backend system (for working with different frameworks, or multiple frameworks at a time) - something I've briefly considered, but started foaming at the mouth as a result."
We should look to Rails 3 JS Helpers for some prior art ... I have a pretty good idea of how we can easily have a widget system that spits out JS of your desired flavor... I just have to write the code.. heh. "These aren't something we could easily incorporate. Just automating JS and CSS bundling and compression would be a big help. This is a good place to start on that:" I have a build-bot that appropriately compresses and versions our JS and GZips it... then sends it off to our CDN. I use a template tag to vary on user-agent to serve up the ungzipped content to IE6. I've found this to be the preferred method over available open-sourced django tags... It does almost zero processing at runtime (just the tag that varies on user-agent). Also I don't like how some of the available libraries encourage concatenization of js/css files that shouldn't be concatenated (that should all be done by hand for best results IMO). -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
