Thanks for the very nice feedback, Levi! :) First of all, I must mention that this is a generalization/reworking of concepts created by equanda, I hope the equanda guys are ok with it being published like this.
I strongly agree with you that the concept demonstrated in this mixin should be integrated into the framework, hence the JIRA issue. There will still be a need for the mixin, but the code required to trigger the zone, optionally with a parameter value provided by the client, should be standardized in some way, making the mixin code a lot simpler and more focused. I haven't seen too many requests for this kind of thing lately, though, so I'm not sure if the committers will pick it up. You should vote for the JIRA! On Wed, Aug 5, 2009 at 9:07 PM, xfile80303 <l...@grokers.net> wrote: > > Hi all, > > I just wanted to take a moment and shine some light onto the "ZoneUpdater" > mixin which appears to have been originally authored by Inge Solvoll. > > For those which are not familiar with it (it took some digging for me to > find it), it is a mixin which will allow one to have an AJAX update occur > for a given Zone, on a specified component event with appropriate handler. > Quite useful. > > See the blog post by Inge: > > > http://tinybits.blogspot.com/2009/05/update-zone-on-any-client-side-event.html > > apparently there is an open JIRA issue related to the implementation: > > https://issues.apache.org/jira/browse/TAP5-521 > > For those Tapestry developers out there who are listening, this is such a > useful and basic mixin that I would suggest it be incorporated into the > Tapestry codebase. If not that, then it should at least be mentioned in > the > wiki or on the related projects page... something. > > Wherever you are Inge, thanks for sharing this very useful mixin with this > community. > > Cheers, > > Levi > > -- > View this message in context: > http://n2.nabble.com/ZoneUpdater-is-Great-tp3394151p3394151.html > Sent from the Tapestry Users 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 > >