OK, I'm new - worked my way through the tutorial, been reading some of the other docs. Really feel the best design principle should be to keep all app related stuff in the app directory (and feel that one day the tutorial docs could reflect this).
So was modifying tutorial to use the app_directories loader Had to take out the 'polls/' subdir part of the template path - that made sense. Working just fine till I get into the part on generic views - out of the box they seem to be generally incompatable with the app_dirs loader. Incompatible is probably too strong a word - less automatic. As stated in the docs for generic views: "If template_name isn't specified, this view will use the template <app_label>/<model_name>_detail.html by default." so if I have a template named: "poll_detail.html" I can't have it in project/polls/templates/poll_detail.html as would be expected for the app_dirs loader, unless I explicitly declare a template_name for each generic view that I use. This is especially true if I use the same template in a generic and custom view. Since the point of generic views is to reduce mundane work, and using app/templates directories I think is very good practice, it surprised me that this issue arose. The simplest workaround was to symlink /project/app/templates to / project/templates/app This allowed me to not have to pass a template name, but felt like a kludge. -Preston --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
