On Mon, Mar 19, 2012 at 11:49 AM, Chris McDonough <[email protected]> wrote: > The asset override stuff also allows you to switch templates for a given > view, if that's all you need. It's documented at > http://docs.pylonsproject.org/projects/pyramid/en/1.3-branch/narr/assets.html#overriding-assets
... if you're using an asset spec for the template. If you're using a filename and depending on the Mako search path, would this still apply? PS. When I read in the docs that you could make a Mako application entirely with asset specs, you wouldn't need the Mako search path, but when I tried it I couldn't get it to work. I may have had the wrong asset syntax, or maybe it was just because my templates have an inherited site template. In any case, I don't think asset specs for Mako will become popular unless there's a way to shorten the syntax. 'renderer="myapp:templates/abc.mako"' takes up so much space it forces you to split the @view_config to multiple lines, which is not the case in its TurboGears and CherryPy predecessors. If I just specify "/abc.mako", it seems to not consider it an asset spec. -- 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.
