> > seconds the templates, they are horrible to code, all the branching > > with SO/SA made me go dizzy, so we need a better approach to building > > templates, and the problem is really with all the branching, for > > example having a full project be build with optional > > SO/SA/identitySO/identitySA, will mean having 4 different templates so > > we really need second the size just look at > > http://trac.turbogears.org/browser/trunk/tg/pastetemplates/turbogears/%2Bpackage%2B > > that's almost 10 folders of stuff, stuff that is going to break > > projects on updates, stuff people are never going to touch because > > they may break something, do we really need ALL that stuff??
Wouldn't it be easier to create multiple templates, using paster's template inheritance feature. We need something that provides an overall TG project structure... As far as SO and non-default templating engine support is concerned, I think we should consider making it's template to be a part of a separate easy-installable package, not part of the core of TurboGears 2. --Mark --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
