Greets all, I'm writing a Django site with various separate planned Django apps; the first one which I recently completed is a contacts management app. It consists mostly of a single Contact object, which has about four or five ForeignKey fields. Some are self-referential and some are to other planned apps within the site.
However, there's a specific ForeignKey which doesn't have a clear spot to live: a contact's 'Category'. It's very simple, just a name, but I felt it would work better as a ForeignKey than as a CharField, for various reasons I won't go into here. I wanted to give the users access to creation and modification of the category listing, but since it's inside the Contacts app, I had to manually write what would've been its generic view functions. This could've been avoided by breaking the Categories out into their own app; but as they have no usefulness outside of the context of Contacts (all the links to them are inside the Contacts templates, for example) that didn't sit well with me. So, I'm curious what the rest of you would do in this situation. Is it better to keep things 'logically' organized, at the possible expense of ease-of-coding (e.g. the ability to use generic views) and possible overcrowding of template directories, or should I always be breaking distinct object types that need CRUD treatment, out into their own apps? Thanks for any thoughts; clearly this isn't a hugely important issue, but my development experience is more limited than I'd like so I'm always eager to soak up the wisdom of those who've been around the block a few times =) Regards, Jeff
