I think an important consideration is that a large number of potential TurboGears users are new or unfamiliar with developing large Python applications. I think this is especially true for those potential users that would use TurboGears for an enterprise level replacement for established web development technologies (they are unlikely to be programming in Python much because they are busy with j2ee, or php, or whatever).
The default layout for the quickstart project is a "deadend" without scalability. It provides a containing wall that requires a developer to stop developing and start learning Python package symantics from another source in order to continue. I think that the quickstart application should provide a scalable starting point to form as the "roots" of a well "grown" large scale application. When it comes time to start breaking code into extra modules and packages, the developer should be able to look to the quickstart as an example of how to do just that. The old adage is that "great code is self documenting". If the quickstart for TurboGears can be a ideal example of how to modularize your TurboGears application for scalability, I think it will be all the better off for it. (As a aside, if someone wants to see a "simpler" version of a TurboGears application, they can always download a sample application from the documentation that is a finished, small application) 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 -~----------~----~----~----~------~----~------~--~---
