> I agree. It's much more reasonable to require some modifications for use > on bigger projects that to incur more boilerplate for everyone.
Everyone? This is a distrubring proposition, that only a few of us will ever have more than one model.py and controller.py Maybe by this same logic we should ditch templates directory because most people will have just 'hello_web.kid'? Perhaps static and css/javascript/images should be flattened too because most people will have one css file, one/none javascript file and a couple of images. No need for hierarchy there. Well, that doesn't work obviously but the reasoning is identical. > > From: Simon Belak <[EMAIL PROTECTED]> > Date: 2006/03/08 Wed AM 11:13:33 GMT > To: [email protected] > Subject: [TurboGears] Re: bike shed #2: controllers.py vs. controllers > directory > > > Michele Cella wrote: > > It's a matter of finding the right balance, I should admit that when I > > tried Pylons/RoR while searching for the supposed way to add a new > > controller I've found myself slowed down in respect to TG, for example > > Django guys some times ago discussed the possibility of reducing the > > base structure of a new project to something like TG. > > I agree. It's much more reasonable to require some modifications for use > on bigger projects that to incur more boilerplate for everyone. > > Cheers, > Simon > > > ----------------------------------------- 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 -~----------~----~----~----~------~----~------~--~---
