On Mar 8, 2006, at 11:41 AM, Ian Bicking wrote: > 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
This is a reasonable argument, and I would actually extend it to say that people who *are* experienced with Python will also have a much easier time finding what they are looking for in a controllers package, rather than a controllers.py file. > Also, models are more intimately interrelated than controllers. > And all the models *have* to be imported up-front, unlike controllers. I think the bottom line is this: model objects are used across an entire application, and are intimately connected through relationships and dependencies. Controllers are much more specialized for a particular part of an application, and are usually logically separate. Again, this argues +1 for a controllers package, and -1 for a models package :) -- Jonathan LaCour http://cleverdevil.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 -~----------~----~----~----~------~----~------~--~---
