I'd put it in a separate, "global" views.py, outside both, like this:
project/ profile/ employment/ urls.py views.py -- Brooks On Apr 16, 5:26 pm, meppum <[EMAIL PROTECTED]> wrote: > I have a Profile app and an Employment app under one project. I've > split these into two applications so I can reuse the Employment one > later as it's generic (it has address, employers, and employment > models in it). I'd like to have a single page for editing a users > profile and their employment information using some jquery javascript > tabs. To do this I'll need a single view that passes both the users > profile record and employment record. > > My question is, where would this view go? In the profile app or the > employment app? It seems like it would be both, but I'm not sure. I > ask only because I'd like to keep in tune with Djangos' DRY principle. > > -meppum --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---