On Mon, 12 Feb 2007 23:19:19 -0500, kbochert <[EMAIL PROTECTED]> wrote:
> >> From the tutorial I see that a project directory looks like: > > Project > App > models.py > views.py > Templates > App > index.htm > Admin > > Doesn't it make more sense to have: > > Project > App > models.py > views.py > Templates > index.htm > Admin > Templates > > Doesn't it work better if the project has multiple apps? > > Templates are found at Project\App\Templates, instead of Project > \Templates\App > Do templates 'belong' to the App or the Project? > > Given that an App consists of models, views and templates, shouldn't > models, views and templates be at the same level? > > I could do this myself using urls.py and settings.py, but isn't admin > hardwired? > You can do it either way, but the suggested way works better when you have multiple apps which share the same layout and who's templates all inherit from the same base template. Add on top of that the fact that (in a large team) you have designers working on the templates (but never looking at python code) and developers working on the code (but never looking at the templates), that approach makes even more sense. Take a look at the source for djangoproject.com [1] and you'll see what I mean. Of course, if each app is completely independent of each other, it's not such a big deal, especially if the developer/designer is one person. That's why you can use the settings to set it up however you want. Do what works for you. [1]: http://code.djangoproject.com/browser/djangoproject.com/django_website -- Waylan Limberg [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
