On Wed, Mar 08, 2006 at 08:47:44AM -0500, Kevin Dangoor wrote: > > On 3/7/06, Jeff Marshall <[EMAIL PROTECTED]> wrote: > > > > +1 for the controllers/ and models/ subdirectory hierarchy. Every time > > I create a new TG project, the first thing I do is create a > > controllers/ subdirectory. I've only had one project that was small > > enough that I stayed within the single controllers.py file. > > For a contrast: the reason quickstart looks the way it does is that I > figured that one would likely start organizing on application terms as > they expand beyond one controllers file. So, rather than creating a > controllers package, one might add an "admin.py" or the like to their > main project package... then, if that starts to get to be a bit much, > refactor into some other set of packages that makes sense for the app. > > I bring that up for background, not to convince people or say that I'm > set on that. > > When you create a controllers package, what's the name of the module > inside that package that you use when you start writing your actual > controllers classes? > > Kevin
I'm just going to throw my 2 cents in right here. We're trying to build a semi-large application with turbogears and still only have a controllers.py file. The reason is because we have seperate directories with models, controllers, and widgets for each of the sections of the application. We did end up having a model directory, but that was only because I wanted to have a project.model.helper package. It was a very simple change, so I don't see the need for a model directory either. I think they should both stay files. Jason -- If you understand, things are just as they are. If you do not understand, things are just as they are.
pgpAw7Ylp3104.pgp
Description: PGP signature
