On Thu, Jun 30, 2011 at 8:53 PM, Chris McDonough <[email protected]> wrote:
> I'd just copy the deformdemo into pyramid_mako and make sure its tests
> pass after changing the copy to use Mako. Rinse, lather, repeat forever
> as you maintain pyramid_mako.
Roger. Right now I can view all the examples in my own browser, but don't
have selenium working yet.
I need a little help with the i18n stuff in the Chameleon templates... I
don't understand what it's doing enough to know how to translate the tal
tags into Mako syntax. Are objects passed into the renderer that I can use?
For example, here's a code snip:
% if field.error:
<li class="errorLi">
<h3 class="errorMsgLbl" i18n:translate="">There was a problem with
your submission</h3>
<p class="errorMsg" i18n:translate="">Errors have been highlighted
below</p>
</li>
% endif
I presume the business bits of this need to look something like:
<h3 class="errorMsgLbl">${_("There was a problem with your
submission")}</h3>
(I tried the _() and translate() and i18n.translate(), but no dice.)
And also how to let Mako cache its naughty bits in the right place... the
Deform docs mention that the example mako conversion is naïve, but I'd like
to do it right. I know that there is a way to do this directly via Mako, but
I'd like to tap-into Pyramid's existing mako cache location machinery in the
case of using Pyramid.
--
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.