I've read hpws, but not the sequel. I suppose following that train of thought, there should be the option for using 2 separate stacks - one for the head of the document, and one for the tail (stylesheets at the top and scripts at the bottom!) > "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:" Yes, I suppose it is. Keeping track of an ordered "set" of resources referenced by a particular view would mean we have a strong place from which to handle that kind of transformation. I wasn't actually planning on bringing that up since at least initially my priority would be to work on ways to keep our frontend code DRY -- just like our python code :) > 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.
