One also attaches panels to layouts and invokes those by name. In other words, while I only played around with pyramid_layout briefly, what I saw as the main feature was the association of a template with a panel name + layout in much the same way that traversal allows associating a view (and renderer/template) with a view name + context. In a sense it provides a way to construct layouts out of modular sub-views bound to sub-contexts.
On Sat, Dec 10, 2016 at 11:01 PM Mike Orr <[email protected]> wrote: > Also, is the Mako usage really as inefficient as it looks? > > <%inherit file="${context['main_template'].uri}"/> > > It looks like it already has the main template object, converts it to > a URI, and then Mako has to look it up agan to get the same template > object it already has. Is this an incompatibility between > pyramid_layout and Mako that requires this kludge? Does it suggest > they don't really go together? > > -- > You received this message because you are subscribed to the Google Groups > "pylons-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/pylons-discuss/CAH9f%3Dupj24j%3D%3D-ZdGCtCsGfSy988wmBEC4OSdMZ60xBLg-LWeQ%40mail.gmail.com > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/CAAL6JQgm2Nvdf15vuM2wELcxqAovz3gQpDwTDJfeVPuwESNDXQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
