Maybe reason is page flexibility. With below template the target address
would always be the same page http://host/site, which is quite static.
But when using the wrapper pattern the callee would be the page (e.g.
http://host/login, http://host/item). this would feel more natural and
layout itself is not exposed as page but as component.
manuel aldana schrieb:
thanks for the link.
looking at this layout injection pattern, i wonder whether a normal
template, which references the dynamic site-parts directly wouldn't be
even easier (i at least find it more intuitive as using the <t:body/>
injection). what are the pros/cons for that?
Site.tml (style stuff omitted):
<html xmlns:t="http://tapestry.apache.org/schema/tapestry_5_0_0.xsd";>
<head>
<t:header/>
</head>
<body>
<t:navigation/>
<t:mainContent/>
</body>
</html>
SergeEby schrieb:
Hi,
<t:body/> is the actual content of your page, and the layout
component is
just a wrapper.
This link would probably help you better understand:
http://wiki.apache.org/tapestry/Tapestry5Layoutcomponent
--
manuel aldana
ald...@gmx.de
software-engineering blog: http://www.aldana-online.de
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
