Re: Dealing with misc parts of a project

2011-09-23 Thread Tom Evans
On Thu, Sep 22, 2011 at 7:04 PM, Simon Connah wrote: > This is one of the areas that I think Django could do with improving on. You > might not have enough functionality to justify turning it into a complete > application but you still want to keep it clean and tidy

Re: Dealing with misc parts of a project

2011-09-22 Thread Simon Connah
On 22/09/2011 19:50, DrBloodmoney wrote: On Thu, Sep 22, 2011 at 12:30 PM, Micky Hulse wrote: On Thu, Sep 22, 2011 at 8:54 AM, Simon Connah wrote: So do you just tend to create a new misc app to hold all these little bits and pieces or is there

Re: Dealing with misc parts of a project

2011-09-22 Thread DrBloodmoney
On Thu, Sep 22, 2011 at 12:30 PM, Micky Hulse wrote: > On Thu, Sep 22, 2011 at 8:54 AM, Simon Connah > wrote: >> So do you just tend to create a new misc app to hold all these little bits >> and pieces or is there a convention for such things? > >

Re: Dealing with misc parts of a project

2011-09-22 Thread Micky Hulse
On Thu, Sep 22, 2011 at 8:54 AM, Simon Connah wrote: > So do you just tend to create a new misc app to hold all these little bits > and pieces or is there a convention for such things? I asked a similar question here:

Dealing with misc parts of a project

2011-09-22 Thread Simon Connah
When writing a project in Django it is a common occurrence that there are some small elements that must be shared between all applications in the project but that do not fit within the context of any of the apps as it would break encapsulation. I'm thinking about things such as terms and