> See those blogs, for example: 4 or 5 classes, 2 or 3 views, 1 or 2 > controllers and > that's it. Nothing more. Is it an irrelevant application? No, I don't think > so. Their authors found it worth writing.
Of course, changing the location of the default controllers and models to an __init__.py file wouldn't have changed the progress of those authors at all. > It is encouraged. You can simply create a new controller, import it in > controllers.py and voi là! It might be that easy, but it's certainly not "encouraged". It's not stated in any way, either indirectly through the quickstart configuration or directly through "how to grow my TG app" documentation anywhere in our documentation. I think one of the best reasons for seperating out controllers and/or models is being overlooked. Yeah, sure, it's "easy to extend your application any way you want" with Python. But developers looking to extend their application aren't looking to do things "any way they want" because that doesn't require any looking at all... just doing. A developer in TurboGears wanting to expand is looking for guidance on best practices that will save him/her the hassle of learning how *not* to do it and fixing it later. The real solution here is two fold: extend the quickstart template to provide an example of "what to do" when building a mature, modular TG application and, second, provide some documentation on best practices for building, extending, and maintaining TG applications. Also, just logically this seems like a little bit of a no brianer. People new to TurboGears are going to learn whatever is put in front of them. This means: Existing Setup: - New users get up to speed and start developing. - Users needing to grow their application stop developing and start researching before getting back to developing. "Modular" Setup: - New users get up to speed and start developing. - User needing to grow their application copy the existing structure to create a new module and keep developing. We lose absolutely nothing by changing the quickstart to a more mature layout, we maintain an inherent barrier to application growth. Who cares how difficult that barrier really is to overcome, if we can remove any barriers to quality development for some of our users without any loss to the rest of the users, then it's a good idea. I mean, that's entirely the point. Travis Bradshaw [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
