Henrik Schlanbusch wrote: > > Hi > > Yes I am aware of this one. To describe my problem, I have a rather big > framework I would like to rebuild from T4 ->T5. In this framework we use a > lot > of tabbed panes. In T4 we loaded pages into each tab. This made our code > cleaner, since we could maintain one tab in one class/page file. My > impression > is that if I start using Zones, I have to implement the zones and their > markup > in one big page. Correct me if I am wrong. > > -Henrik >
You have two options: 1. you put your tab contents into components and add them all components to the tab page. Here, you have the whole power of Tapestry parameters. 2. you keep tab contents on separate pages. With this you lose the power of parameters and have to hand over parameters to tabs and between tabs via some threaded context service. For the page solution you have to put the contents into a block and get the block into the othere page (like described here by Taha: http://tawus.wordpress.com/2011/04/20/tapestry-magic-3-plugin-blocks/). We've coded a small BlockService you can contribute to blocks to and get them on another page. -- Chris -- View this message in context: http://tapestry.1045711.n5.nabble.com/Page-as-Ajax-return-tp4864551p4864692.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
