On Oct 17, 1:06 pm, stv <[EMAIL PROTECTED]> wrote: > really? I'm researching Django for a potentially large project, I was > thinking of having a layout like this: > > mainproject > |--core # models reused everywhere: Person, Address, etc > |--apply # models only for application: Questions, references, etc > |--enroll # models for enrollment, mostly core, maybe 1 or 2 extras. > > and so one ... thinking that when I develop in the apply app I'll only have to > > from mainproject.core import Person > > and so on ... Does this not work as easily as I am hoping? I'm > guessing core won't have much (any?) templates/views, all that being > handled in the sub applications ... > > But I'm just getting into Django design ... so I may be way off base
I think what you'll end up with is more like: from mainproject.core.models import Person from mainproject.apply.models import Application from mainproject.enroll.models import LicenseAgreement It was this 'model proliferation' that moved me back towards having one application per project. But my projects aren't that big, and having my Models in one place works for me. I can still break up the views into more logical sections, based on functionality, e.g., views.apply, views.enroll. Your larger project may benefit from breaking the apps up, if for no other reason than a reduction in merging during checkins. Like I said, I tried it with many apps, but for my projects and the way I was working them, I didn't see the advantage. Go with multiple apps and see how it works for you. Just write lots of tests so you can refactor later without fear. doug. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
