Regarding explicit use of RenderCommand; yes - this was clearly pent-up
paranoia!
Checked the response and it looked good as I was writing and then came
across a happy little solution!
>Anyway, if you want to update a zone, you shouldn't use jQuery.ajax()
>directly, but use the ZoneManager JavaScript class instead.
I'm a bit fuzzy on this but I'll poke around the ZoneManager and see what I
can work out.
One thing I'm messing around with in the mixin is to do something similar to
EventLink;
1) pass in a zone id
2) pass the zone id into the mixin js initializer parameters
3) if zone is defined do;
$("#zone").tapestryZone("update", {url : parameters.url, params :
undefined
})
(so along the lines of an event-type agnostic
ClientBehaviourSupport.linkZone, hacky, cutty, copy, pastey).
This is currently working. Wow. A couple of niggles to work out but I think
it's almost there!
Yay indeed! I'll keep bashing my head against this; I believe it'll be a
really handy mix-in to have in stow. I'd be more than happy to show the code
but I guess I will need to clear it with the firm before doing so.
Thanks for the help Thiago - will be back to post the code if I'm able once
it's fully unit tested and clean. :)
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/ComponentEventResultProcessor-for-a-triggered-event-tp5715657p5715672.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
