On Feb 20, 11:30 am, Ivan Sagalaev <[EMAIL PROTECTED]> wrote: > But I suppose that you are talking about using MEDIA_URL to access CSS > and JS files, right? If yes then it's not what everyone does. Many > people keep CSS and JS under source control in a place that has nothing > to do with a directory for user uploads. So why expose MEDIA_URL in > templates?
Not just uploaded images, but images, flash, css etc that are part of the site design too. To me, the framework seemed to encourage delivery of flat media (images, css, js, anything flat) via a separate path, even separate server. In my experience, maintaining a separate tree, and an easily changeable setting pointing to it, is a very good practice to encourage. I like it. Thats why TEMPLATE_CONTEXT_CONSTANTS seems sensible to me. It's very useful for things like Google Maps API keys, copyright entities, html-head suffixes, all sorts of things. Without having to resort people, new users especially, to using context_processors and RequestContext. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
