On May 27, 2010, at 5:27 PM, burc...@gmail.com wrote: > Hi all, > >> - a media files path resolver -- following a similar directory structure as >> the app templates loader (<app>/media/<app> vs. <app>/templates/<app>) >> - build_static -- a mangement command that'll collect media files from apps >> from various locations using the media files path resolver and uses a file >> storage backend to copy (or link to) the found files (file storage backend >> by default), used during deployment >> - an extended media file serving view that uses the media files path >> resolver (in debug mode), backwards compatible replacement for >> django.core.servers.basehttp.AdminMediaHandler > > Couldn't agree more. But three more points: > 1) Media files are linked from applications forms, so what will happen > if user rename an app?
If someone changes the name of the app there is no way they will get by without modifying source code in the app. Why should this be any different? I wouldn't really buy the argument that it reduces the amount of change they'd have to do. It applies to the convention people use when storing/referencing templates too. Brian Rosner http://oebfare.com http://twitter.com/brosner -- 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.
