This issue existed on SourceForge. The original can be viewed at https://sourceforge.net/p/turbogears2/tickets/117
Original Author: pedersen, Original Timestamp: 2011-09-19 17:26:48.547000
Original Body: In talking with Chris Perkins, we wound up stumbling across an idea that I think has some strong merit.
We should find a way to extract SQLAlchemy, Ming, ToscaWidgets1 and ToscaWidgets2, along with other options, into more modular templates. Right now, we have a lot of "if" statements, everything packed togther, and not much modularity for reuse.
I'm not sure if we should make external modules, or just work out a new structure for the templates that will allow them to be more modular/easily updated. I just know we should look for ways to improve the overall structure of tg.devtools.
Original Author: amolsf, Original Timestamp: 2011-09-19 19:34:00.269000
Original Body: This is something that must absolutely be done with making an automation for extensions (something like django-app). As the most difficult part for this is not adapting the tg.configuration module but making a reusable solution for the quickstart template itself we should consider doing something splitting in microtemplates the quickstart template. For example, by having the auth.py model composed by multiple microtemplates for imports, user, group etc, it would be possible to replace only the template of the User model without touching everything else.
Original Author: godoy, Original Timestamp: 2011-10-02 11:46:09.723000
Original Body: I have looked for means to use entrypoints on the templates as well. Using the standard approach gives some level of success, but all what I did at runtime.
I wonder if there are means to get entrypoints with some standard text and use that on our templates. Providing those would become part of the API and we can create some default code until others adapt.
This can be used for the application template as well as for the (X)HTML templates that will be rendered later.