Hi
Thanks for the input.
I agree with your points and my experience is also that mostly things just
work or you are provided with a helpful error (my naming is to avoid having
to change all the pages that currently refers to "layout" while testing ;)
I have managed to get it to work. I had screw
What you're trying to do is quite common and always works fine in my
experience. In fact this sort of composition is preferred over having a
shared base class. I often have a main "Layout" component along with more
specialized layout components for different sections of a site (e.g.,
AuthenticatedL
Hi
I'm trying to improve on the layout we are using across several tapestry
based products.
Initially it used an abstract base layout component that the products
extend to provide a common line for the layout.
I'm trying to simplify this situation by making the layout in the framework
module a co
