[EMAIL PROTECTED] wrote: > >> 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
I regularly have 2000 line model files, and it doesn't bother me at all. Well, okay, a little. But splitting each table into its own file would be a poor solution. A better solution would be factoring out the actual logic that causes it to get so big. Partitioning is a poor way of managing complexity in this case. Controllers are somewhat different. One issue is that people without much experience can useful edit controllers, but will have problems navigating a giant file. Those same people can't really usefully edit the models anyway. Also, models are more intimately interrelated than controllers. And all the models *have* to be imported up-front, unlike controllers. -- Ian Bicking / [EMAIL PROTECTED] / http://blog.ianbicking.org --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
