Thanks for the quick response!
Hm, I didn't know that this would break the class hierarchy.
I understand the issue like this (hope it works in HTML/Mail):
Layout.tml > Page.tml --> Result <-- Page.java < BasePageRed.java <
BasePage.java
[read P]
[Set P] [Declare P]
I am far from completely grasping what goes on when Tapestry renders, but I
though the tmls ('left') and classes ('right') are merged somehow.
I assumed I could tell Layout to 'expect' a Parameter coming from the class
side.
Alternatively, setting the parameter in every Page.tml (few dozen) just
didn't seem so 'DRY'.
But your solution sounds very reasonable - I was just wondering :-)
Cheers
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Customizing-the-Layout-Component-tp4234938p4235829.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
