Nice one, Thiago. https://issues.apache.org/jira/browse/TAP5-2301.
On 15/03/2014, at 4:51 AM, Thiago H de Paula Figueiredo wrote:
On Thu, 13 Mar 2014 23:32:55 -0300, Geoff Callender
geoff.callender.jumpst...@gmail.com wrote:
To all Tapestry devs,
Hi!
I agree with you. That's one of
Chris,
In case you haven't seen it, I explored some of the issues of Grid, filtering,
and AJAX here:
http://jumpstart.doublenegative.com.au/jumpstart7/together/ajaxcomponentscrud/persons
Don't know if there are any useful ideas in there for you.
Geoff
On 14/03/2014, at 8:15 PM,
It's probably worth mentioning my onevent mixin here.
http://tapestry-stitch.uklance.cloudbees.net/oneventdemo
Sorry to toot my own horn but I think it greatly simplifies many ajax
interactions. It not only allows a context to be passed but it can also
send a list of clientside field values in
Yes, I think it should be part of tapestry core.
As a nod to jquery you could simply call it on :-)
On 15/03/2014, at 6:39 PM, Lance Java wrote:
It's probably worth mentioning my onevent mixin here.
http://tapestry-stitch.uklance.cloudbees.net/oneventdemo
Sorry to toot my own horn but I
Yes, I think it should be part of tapestry core.
Unfortunately it clashes a bit with the zone parameter in select. Does
anybody support making a breaking change to remove the ajax behaviour from
select if this mixin was added to core?
As a nod to jquery you could simply call it on :-)
Yeah, I
