Ned Batchelder wrote: > We're about to embark on adding a major chunk of new functionality to my > Django app. My question is, how do I decide whether to make it a new > Django app, or whether to simply add the models and views needed into my > existing app? > > What are the rules of thumb that you've used in the past to decide > whether something is a new app or not?
With Django I've been using about the same guidelines I would use in any other Object Oriented project. Basically, for me, Projects are namespaces and Apps are libraries, and I just try to follow good code modularization principles. -- --Max Battcher-- http://www.worldmaker.net/ "I'm gonna win, trust in me / I have come to save this world / and in the end I'll get the grrrl!" --Machinae Supremacy, Hero (Promo Track) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
