Yep, you'll have some overlap, but I think it makes sense to create a separate app wherever the data model/views could logically stand alone. So, user registration would be one app. I'm working on a project that does a lot with demographic data based on user profiles, so profiles is another separate app, but both import the User object. And then your survey mechanism would be yet another app, and so on and so on.
On Sep 13, 10:39 am, mickeyckm <[EMAIL PROTECTED]> wrote: > I'm a little confuse as to when to create an app. > > I'm trying to create a survey project. Is user registration an app on > its own, the part where the person login/register? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
