Hello,
I've found that each application should be specific in its
functionality. How you organize it really depends on the type of
project. A simple blog might only be one application. Our intranet
site has 7, including a settings.py file, if necessary.
I think how coupled or decoupled you can make applications depends on
the project. For example I have several applications that do very
specific functionality, but all of them rely on a shared set of
tables that I've grouped into a "Core" application. In the same
project I have apps that are completely independent.
If you post more description of your project, I'd be happy to give
you some suggestions.
Corey
On Jan 16, 2007, at 4:56 AM, [EMAIL PROTECTED] wrote:
Hi community,
Been playing with Django for a while now, but I am still confused
about the
separation of applications within a project. So far, I end up either
implementing all my features within one Django app, or having too
many direct
connections between my apps, making each of them unexportable for
reuse in
another project.
I wanted to share my concern, in order to get valuable feedback on
effective
independency of Django applications.
Does everyone manage to get loosely coupled applications in their
projects? Any
tips to share? Is my twisted mind unrecoverable?
Thanks in advance.
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
