Joseph Kocherhans wrote:
> Any ideas that don't involve 50+ character table names and 10 level
> deep template directories? ;-)
What about application relabeling? Just like you might do a python
``import something as somebettername`` when there are conflicts across
namespaces or you just want something nicer in your actual code, you
could just add an "as" option to INSTALLED_APPS to specify an app name.
Very cool idea. This can solve the problem of table names and keeps admin urls simpler. But templates is still something you have to worry about, and one solution is to keep a module name based structure in template directory, but a better solution could be to make template system aware of the current app, let it query django to find the "as" name name, and use that as a prefix to all template paths.
And ofcourse django-admin.py may contain a "rename app" command, just in case you later changed your mind about their name which renames all the tables in the database, as well as all the matching subfolders in all template directories.
--
Amit Upadhyay
Blog: http://www.rootshell.be/~upadhyay
+91-9867-359-701
