Hi Waldemar, On Fri, Oct 29, 2010 at 2:05 PM, Waldemar Kornewald <wkornew...@gmail.com> wrote: > Hi Carl, > >> As I read it, your option 4 means putting URLs into CSS files that >> will not resolve correctly if static files are served directly, >> unmodified, from their source locations (after being collected from >> apps) under STATICFILES_URL (because the URLs you give don't begin >> with a slash, so they will be interpreted as relative to the current >> location; and if they did begin with a slash, that would break anytime >> STATICFILES_URL is not a path-less domain). In other words, you are >> proposing to write CSS files that _depend_ on being run through some >> kind of combiner/compressor/filter that will intelligently rewrite all >> their URLs relative to STATICFILES_URL. As a proposal for a >> "standard," this is a non-starter for several reasons: Do you agree with that "you are proposing to write CSS files that _depend_ on being run through some kind of combiner/compressor/filter that will intelligently rewrite all their URLs relative to STATICFILES_URL"?
If you do, then you understand that you're trying to impose a standard for django users that is really unnecessary for them? You're free to allow such perversion with your app, but please don't try to put this into django. Why can't you read css files, transform their paths to absolute, merge files, and then write paths back as relative to merged files? -- Best regards, Yuri V. Baburov, ICQ# 99934676, Skype: yuri.baburov, MSN: bu...@live.com -- 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.
