I'm not 100% exactly what you're trying to do but it sounds like you should make components for the bits you want to re-use and then pass a block parameter to the layout.
Take a look at the RenderCommand class too. This is a way of providing markup programatically and it may make sense for you to use a RenderCommand parameter instead. You can use Tapestry's type coercion to convert from Block to RenderCommand. Inheritance is almost always a bad idea and more often than not, there is a more elegant way of doing it in tapestry. Pages and components can implement interfaces, but the interfaces MUST must not be in the pages or components packages. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Sidepanel-with-pagespecific-items-tp5679939p5680458.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
