@Lance and @Taha - I can see how this might alleviate some of the large numbers of zones I'm passing around as parameters to components though I really still don't like the idea of keeping a bunch of references to zone instances anywhere apart from perhaps at their point of injection in their 'home' component. In my understanding once a zone is declared it is known to exist by the client-side by its unique client id; would be nice to just be able to invoke AjaxResponseRenderer.addRender off that unique client id rather than passing the zones around all over the place.
@Howard - yes I've experienced this 'ordering' issue myself also! Must say I really am loving the sound of 5.4 more and more after reading your blog post a couple weeks back. The '^' short-cut is very handy indeed but I am specifically interested in your comment about specifying specific client ids for the zones so that I don't have to carry the instance around. I declare my zones as such <t:zone t:id="someid" id="someid">...</t:zone> giving them their specific client id. I then need to update multiple zones (via AjaxResponseRenderer) but the addRender methods require either the Zone itself or the zone's id and a renderer (thus I will usually end up going AjaxResponseRenderer.addRender(zone.getClientId(), zone and so have carried the zone instance around with me). Is there something that I'm perhaps missing or are you alluding to a way of updating zones solely via their unique client id? I can imagine a mixin that might simply invoke zone updates for provided client ids... but how else might this be possible unless I explicitly specify or construct the 'renderer' in every place that addRender might need to be called? And thanks all for your responses! It's very exciting to be able to build such complex pages with real relative ease! -- View this message in context: http://tapestry.1045711.n5.nabble.com/Elegant-Handling-of-Multiple-Zones-in-Deep-Hierarchies-of-Components-tp5717698p5717760.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
