Joel, I'd use application state objects to share state between them. This is a nicely decoupled solution. See http://tapestry.apache.org/tapestry5/guide/appstate.html
Bill On Sun, Oct 12, 2008 at 12:48 PM, Joel Halbert <[EMAIL PROTECTED]> wrote: > Hi, > > I'm not sure what the correct T5 pattern to apply to the following page > composition situation: > > I have a typical scenario - a page with 3 elements a "top nav", a "side nav" > and a "content pane". > > I wish to reuse the code for "topNav" and "sideNav" but i want the content > pane to vary (i.e. it might be a "list" or it might be a "detail"). > > If I use Components for each I find it hard to share state between all three > (as is my need), what I really want to do is simply have a base tml file, > containing the "topNav" and "sideNav" and a class for the associated logic > which I can then extend depending using various classes and tml files that > will provide "content". > > How would this best be achieved? > > Thanks, > Joel > > > -- > SU3 Analytics Ltd > 61b Oxford Gardens > W10 5UJ > London > > Tel: +44 20 8960 2634 > Mob: +44 75 2501 0825 > www.su3analytics.com > > SU3 Analytics Ltd is a company registered in England and Wales under company > number 06639473 at registered address 61b Oxford Gardens, London W10 5UJ, > United Kingdom. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Without coding you have no product Without testing, no quality Without refactoring, no future --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
