On Mon, Apr 20, 2009 at 8:06 AM, Florent Aide <[email protected]> wrote: > > On Mon, Apr 20, 2009 at 11:42 AM, Diez B. Roggisch <[email protected]> wrote: >> >>> One major thing that I'd like to see worked out in 2.1 is better >>> handling of the way we load and render templates. In my mind we >>> should switch to using the native template loaders from genshi, mako, >>> etc -- or we should create a separate "dotted notation" loader package >>> that contains just the code that loads templates based on python path >>> like notation. There are advantages to both ways of doing things, >>> but we need to choose between them and then commit to that path. > > I have worked a lot on this and already added some more template > loader support in 2.1 > Dotted names support is the easiest way I see to easily support > extension (think Pages)... > > I am also in favor of moving the template (moving and rendering) in > another subpackage not directly in tg.core. In this I would like to > decouple tg from pylons.templating.render_xx()
I'm not totally sure why search paths wouldn't work for extensions like pages. You have to use actual paths, but it's very easy to overide the template of an extension by putting something higher up the list of paths to check (like in your app code). I've used this in a couple projects where we had re-usable chunks and it worked out well. But I'd believe that there's something I'm missing, just not sure what it is yet ;) Unless what's missing is support for extensions to be zipped eggs.... --Mark Ramm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
