On Thu, Oct 28, 2010 at 4:41 PM, Waldemar Kornewald <wkornew...@gmail.com> wrote: > What's the problem with all of this? Code written for (1) is > incompatible with code written for (2) which is incompatible with code > written for (4). The asset managers listed on djangopackages use any > of those three methods. There is no agreement and none of those > methods seems to be preferred: > * django-compressor: (2) > * django-mediasync: (1) > * django-compress: (1) > * django-mediagenerator: (4) > * django-static: (4) > * django-static-media-manager: (1) > * django-assets: (2)
BTW, if the combined output CSS file is always placed into the root folder (static_root/main.css) then code written for method (1) is compatible with method (4). Bye, Waldemar -- Django on App Engine, MongoDB, ...? Browser-side Python? It's open-source: http://www.allbuttonspressed.com/blog/django -- 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.
