On 10/22/05, Jeffrey E. Forcier <[EMAIL PROTECTED]> wrote: > 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?
That's a great question. The natural shift at World Online was that we started with a small number of big apps and eventually split them into a large number of small apps. In fact, we had a "category" model -- pretty much like your example -- that was originally in another app, and we ended up factoring it out into its own app. Of course, with that said, World Online has dozens of Django apps, reused across several sites, so it makes sense to split things up. If you're working on something small that you won't need to reuse, there's no disadvantage in packaging things in the same app. Ultimately, it's really easy to split things up after the fact -- it amounts to moving a couple of files and changing a couple of import statements. I realize this doesn't give you a definitive answer, but I hope it helps somehow. :) Adrian -- Adrian Holovaty holovaty.com | djangoproject.com | chicagocrime.org
