On Tue, Jan 8, 2013 at 10:30 AM, Lachlan Musicman <[email protected]> wrote: > On Tue, Jan 8, 2013 at 9:52 AM, chad petzoldt <[email protected]> wrote: >> Right now my project only has 2 apps that use a database (*real* apps). The >> rest of the website is composed of many custom views, scattered all over the >> place. I am new to Django, and I havn't quite figured out how to structure >> my project directory just yet.
> I think that splitting each article into it's own app sounds like a > disaster waiting to happen. A massive clusterfuck of disaster. The > idea of apps is to abstract out any commonalities to make workflow and > presentation more simple. It is possible, but you need to do the > mental abstracting. Personally I use trial and error - implement > obvious solution, make changes as more complexity is required. My > sites are simple. For more complex apps, you might want to sit down > with a text/UML editor and flesh it out first. Get other eyeballs on > the abstraction too! I'm glad Mario was so positive. I didn't mean to be so negative. I was imagining over 10-20 articles. At which point *I* see it as unmanageable. *I* see it. Others might be happy with more than twenty or so apps. It's a matter of preference. What happens if there are over 100 apps? Cheers L. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. 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.
