On 14 Apr., 11:45, "James Bennett" <[EMAIL PROTECTED]> wrote: > On Thu, Apr 10, 2008 at 2:49 AM, jurian <[EMAIL PROTECTED]> wrote: > > Does anyone else think I should add a ticket request for this as a > > future feature? > > I'm ambivalent, but leaning toward "no". In my experience, it's very > rare to have media files that are truly coupled to a single specific > application; django.contrib.admin is the only example I can think of. > This is a consequence of the fact that, most of the time, media files > vary from site to site -- Site A uses this stylesheet and this icon > set and this JavaScript toolkit, but Site B has its own styles, its > own icon set and uses a different JS toolkit.
I agree that you can't always reuse those media files, but why does that mean there shouldn't be an easy (automatic) way to serve media files? There still is the global media folder and quite a few novice users would have an easier time getting started with Django. Even advanced developers could save those few lines of code which repeat in every project, anyway. And if we're already at it we can do it correctly and serve the admin media folder automatically, too. Also, at least in our case, we do have reusable components which need their own media folder. E.g., we have a JavaScript text-field autocompletion app. It would even be much easier to extend Django with JavaScript support by putting the code into its own app with its own media folder. Bye, Waldemar Kornewald --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
