> I didn't make that switch at this point because, by convention, > TurboGears model classes are in yourproject.model. I wanted to avoid > breaking other tools (tg-admin sql create, CatWalk, etc).
Ah right, ok. The way I've rigged my project is to still have a model.py file but it imports models from a models directory. That's how I did controllers too. I still have a controller.py (root) file but it just imports from a controllers directory. I haven't used 'sql create' or CatWalk so I'm assuming that when I do they'll put stuff into my model.py and I should be ok? > > From: "Kevin Dangoor" <[EMAIL PROTECTED]> > Date: 2006/03/23 Thu AM 03:37:33 GMT > To: [email protected] > Subject: [TurboGears] Re: bike shed #2: controllers.py vs. controllers > > > On 3/22/06, Justin Johnson <[EMAIL PROTECTED]> wrote: > > > > > > That seems fair enough. Start small if you like and upgrade when you > > need. Or, as I probably will, start with tgbig to begin with and be > > done with it. :-) > > > > I'm guessing that tgbig doesn't cater for a models directory with > > individual model files currently? > > I didn't make that switch at this point because, by convention, > TurboGears model classes are in yourproject.model. I wanted to avoid > breaking other tools (tg-admin sql create, CatWalk, etc). > > The controllers change is pretty transparent. > > Kevin > > > ----------------------------------------- Email sent from www.ntlworld.com Virus-checked using McAfee(R) Software Visit www.ntlworld.com/security for more information --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears -~----------~----~----~----~------~----~------~--~---
