My app does roughly the same thing and is organised as thus:
- each module has its own app (invoices, emails, stuff_we_sell...).
The app contains the models with most of the business logic and the
managing views (for our own use)
- a separate client access module that wraps around some of the
mana
I'm sorry. My example is a bit misleading (actually a confusing mess),
but the reason for splitting off models into separate was just my idea
of a means to an end but probably is a bad solution. I should have
started with my business problem instead of mingling my solution into
the explanation.
Le
On Mon, Jun 21, 2010 at 10:07 AM, M Rotch wrote:
> I just have a few practical ideas that I want to lay out, pertaining
> to loose coupling.
>
> I've worked with Django for a while and one of the things I love is
> that you can do things your own way, instead of having the
> constricting requireme
I just have a few practical ideas that I want to lay out, pertaining
to loose coupling.
I've worked with Django for a while and one of the things I love is
that you can do things your own way, instead of having the
constricting requirements that "convention over configuration" brings
(like in Rail
