^^ Yah that's how I currently do it, but I think it would be nice to have a separate set of "default" templates for each renderer. Any way we could easily do that Chris? Like have a configuration setting of some kind in the .ini possibly, where you can choose the renderer that deform uses by default. Because the method you linked above would be nice for the more obscure template renderers, but I think it might be good to include Mako by default as well as Chameleon, as Mako is very popular.
On Thu, Jun 23, 2011 at 2:24 PM, Chris McDonough <[email protected]> wrote: > On Thu, 2011-06-23 at 11:25 -0700, Mike Orr wrote: >> On Thu, Jun 23, 2011 at 7:16 AM, Joe Dallago <[email protected]> wrote: >> > I would like to help with this, if you guys start a project. I would >> > say the best way to do it would be to alter deform to accept multiple >> > template rendering engines stored within deform itself. > > It already does: > > http://docs.pylonsproject.org/projects/deform/dev/templates.html#creating-a-renderer-using-an-alternative-templating-system > > - C > > > -- > You received this message because you are subscribed to the Google Groups > "pylons-discuss" 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/pylons-discuss?hl=en. > > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en.
