I'm trying to normalize all of the paster templates in Pyramid, so they
share a single BeforeRender subscriber. The BeforeRender subscriber
in each paster template will add keys to the top-level set of names that
can be used within every renderer (for example, within a Mako or
Chameleon
On Wed, Nov 10, 2010 at 5:00 PM, Chris McDonough chr...@plope.com wrote:
I'm trying to normalize all of the paster templates in Pyramid, so they
share a single BeforeRender subscriber. The BeforeRender subscriber
in each paster template will add keys to the top-level set of names that
can be
On Wed, 2010-11-10 at 19:26 -0800, Mike Orr wrote:
'c', 'h', and 'url' are most important.
Thanks, that's what I figured. Most folks on IRC agree (at least they
said c and h are probably non-negotiable).
'url' is very heavily used; e.g.,
${h.link_to(Link title, url(routename, var1=val1)}
On Wed, Nov 10, 2010 at 9:08 PM, Chris McDonough chr...@plope.com wrote:
On Wed, 2010-11-10 at 19:26 -0800, Mike Orr wrote:
'c', 'h', and 'url' are most important.
Thanks, that's what I figured. Most folks on IRC agree (at least they
said c and h are probably non-negotiable).
'c' is still
On Wed, 2010-11-10 at 20:05 -0800, Mike Orr wrote:
I think we need to think strategically about Pyramid's application
templates.
Agreed.
There are already eight of them, with overlapping
functionality and inconsistent names. There will probably be more
templates coming, both bundled with
On Wed, 2010-11-10 at 21:53 -0800, Mike Orr wrote:
We don't have url in there now. The equivalent of url (as of about
2 hours ago when I checked it in) would be:
${request.route_url('routename', var1='val1')}
I'm hoping this is sufficient to supplant url.
I think 'url' is
Am 11.11.2010 05:05 schrieb Mike Orr:
I think we need to think strategically about Pyramid's application
templates. There are already eight of them, with overlapping
functionality and inconsistent names. There will probably be more
templates coming, both bundled with Pyramid and separate. ChrisM
