As my 0.02 cents of new comer I can confirm this was one of the things that
slows adoption of Django. Proposed change to have ADMIN_MEDIA_PREFIX to be
/admin_media/ (or either /media/admin/ ) makes more sense (at least for me).
When I started with django I was confused with when I used /media for my
media (as suggested in doc) just to find out my admin section is not working
properly anymore. I either copy the admin folder from <somwhere to django
installation folder> to /media or I now change ADMIN_MEDIA_PREFIX to be
/admin_media/ and setup a static server in my urls.conf and I'm pretty sure
this not the right way anyway (it works but not out of the box).

Than I had to disturb people in IRC and mailing lists and I'm pretty sure a
lot of newcomers do the same. And since you promote DJANGO to be easy to use
you have to expect really newcomers with hardly any Apache, project folder
organization, mod_python experience at all. Not gurus like you are, for whom
this seems such a trivial change to not even bother with it. This is when I
find Yuris comment about not understanding your users requirements to be
correct and valid.

Although I like Django very much I really cannot understand why there is
such a lot of everyones effort wasted on such a small and clean up  or
cosmetic (remember django fav icon issue?) changes instead of just doing
them. I use 0.96 and I'm pretty sure the SVN code is already a lot of
backward incompatible right?

all the best

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@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-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to