On 7/2/07, Mark Ramm <[EMAIL PROTECTED]> wrote: > > > > 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. > I actually try that a while ago but i ditch the idea because we will have ended up with even more templates, if I remember correctly the biggest problem was not with SO/SA but with SO vs SO+identity because I couldn't find a way to have a template append or insert data into another so, model.py should be put in both SO and SO_identity which means that we'll end up with 4 different model.py files, which means that everytime an update to the model.py was made we'll have to fix it 4 times.
> We need something that provides an overall TG project structure... > I agree, although over the time the overall project has been growing and growing back in TG 0.7 or something, the template was about 10 files right now in TG2 is reaching 30+ and some are even importing "the infamous pylons one letter globals"... for example last night I had to port a project from 0.9.6 or something to trunk, since the upgrade never really worked I had to ran a diff which showed up 100s of differences mainly because of the package names being put almost everywhere on the generated files Honestly I have no answer for this but I think we should find a way to reduce the ammount of generated code. > 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. yes I think we discuss this a while ago but noone wanted to maintain it, maybe because the original structure was so messed up, although fred has already done some work on this with genshi-quickstart, now the question is should we have one package with all extras or several packages one for each? I believe that the one package approach defeats the purpose as your pulling in a lot of cruft but many packages may become a maintenance problem. > > --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 -~----------~----~----~----~------~----~------~--~---
