Can anyone chime in with an opinion on this question ?

Thiago - you usually have words of wisdom - would you share your thoughts,
how would you approach this ?

Regards,

Alex K


On Sat, May 8, 2010 at 8:58 PM, akochnev_chub <akoch...@commercehub.com>wrote:

>
> I'm working on something that I think is very common functionality : I have
> a
> form that's submitted over ajax (using the form's zone parameter). However,
> I would like to clear field values after the form is submitted. I can think
> of a couple of different ways to do it, but I don't seem to like neither.
> Ideally, I would have liked to have the prototype ajax events exposed
> somehow (e.g. similarly to the way grails has a <g:remoteLink onSuccess="'
> onFailure="" />)
>
> 1. The initial thought is that I should be able to hang a listener off the
> submit event of the form itself, but I read on the list that the T5 event
> handling swallows the event.
>
> 2. I could try to listen for the Tapestry.ZONE_UPDATED_EVENT event and
> clear
> the form . That kinda sucks since I would be notified on all zone updates
> and have to figure out if I need to clear the form
>
> 3. I could provide a function for the zone's "show" and "update" params,
> then clear the form from there. I once again don't like this as this places
> the responsibility to clear the form to somewhere outside of the form.
>
> So, what would be the proper way to hang off some post-processing logic
> after form submission Tapestry style ?
> --
> View this message in context:
> http://old.nabble.com/Ajax-event-hooks-T5-style-tp28499704p28499704.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
>
>

Reply via email to