On Thu, Jun 23, 2011 at 3:38 PM, Chris McDonough <[email protected]> wrote: > On Thu, 2011-06-23 at 16:32 -0500, Joe Dallago wrote: >> ^^ 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. > > I'd make a deform_mako package, put the templates in there, and tell > folks how to configure deform to use those templates in the deform_mako > docs.
How close is Deform coming to being a standard or the most widely-used form library? Is it ready to get an optional configuration in Akhet? If so, somebody would need to tell me what the configuration should be. Note that Akhet uses Mako by default, so the Deform configuration would have to too. (Well, it doesn't strictly have to, but if we're close to having Mako templates for all the standard widgets, it might as well enable that from the get-go.) -- Mike Orr <[email protected]> -- 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.
