Thanks a lot for the info, Barry!
Will definitely check it out.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Customizing-the-Layout-Component-tp4234938p4258643.html
Sent from the Tapestry - User mailing list archive at Nabble.com
If you have a Blue/Red that inherit from BasePage I'd use a Layout
Environmental. Since you have a BasePage you can create the Environmental in
your BasePage class. The Red/Blue pages should be able to set the color
property and then the layout component can retrieve it. That way only those 4
c
On Mon, 21 Mar 2011 15:22:30 -0300, stephanos2k
wrote:
Thanks for the quick response!
Hm, I didn't know that this would break the class hierarchy.
It doesn't.
I understand the issue like this (hope it works in HTML/Mail):
Layout.tml > Page.tml --> Result <-- Page.java < BasePageRed.java <
rameter 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/Cust
On Mon, 21 Mar 2011 14:27:35 -0300, stephanos2k
wrote:
In my Layout I'd like to distinguish between 2 states (let's just say
red or blue). Those are known/set by each page individually - it
inherits from BasePageRed or BasePageBlue (which go back to BasePage
where the parameter Col is
d
ue from the BasePage (class) to the Layout
(tml)?
PS: I am aware that I can set the parameter in Page.tml - but I don't want
to repeat myself in each file.
Cheers,
Stephanos
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Customizing-the-Layout-Component-tp4234938p4
