On 2/15/07, James Tauber <[EMAIL PROTECTED]> wrote: > That would be great. In fact, it would be nice if many of the > component apps of the site were themselves available on the site for > building other software component catalog sites.
Absolutely. I'm a fan of open-source sites (hopefully going to be launching one soon!). > What do you think of the idea of having (optional) conventions for > improving the ability of apps to work together? I've come across a few useful things I've been meaning to write up, but I've already got a huge backlog of blog entries I need to finish :) I think that a lot of it comes down to four things: 1. Good conventions for code structure, so things end up in predictable locations. 2. Use of the "app directories" template loader so you can distribute sample templates with the app. 3. Careful import statements which don't rely on the name of an overarching project (which isn't hard, but a little different setup from when people do a project where all the apps live in directories under the project dir). 4. Documentation. Can't stress this one enough: having both standalone documentation and docstrings and comments throughout the code can make or break an app's reusability. Anybody else got thoughts on useful ways to help the reusability of a Django app? There are some other minor things like how to safely handle custom SQL, but the four I've listed are, in my experience, the big ones. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
