+1 vote for this, I previously raised this last January.
https://issues.apache.org/jira/browse/TAP5-1404
On 6/01/2012 7:37 AM, Igor Drobiazko wrote:
This not a good idea, as we consequently would need to provide
AjaxActionLink, AjaxPageLink, AjaxForm, etc.
On Thu, Jan 5, 2012 at 9:02 PM, Muhammad Gelbana<m.gelb...@gmail.com>wrote:
Or maybe a whole new component with a whole different name ? Instead of
EventLink we can have AjaxEventLink or something..just an idea.
I bet you will find this page very interesting Lance
http://tawus.wordpress.com/2011/10/01/tapestry-5-3-new-features-part-2/ It
demonstrates many different flavors of ajax calls in tapestry.
On Thu, Jan 5, 2012 at 8:09 PM, Dragan Sahpaski
<dragan.sahpa...@gmail.com>wrote:
On Thu, Jan 5, 2012 at 5:35 PM, Igor Drobiazko<igor.drobia...@gmail.com
wrote:
Maybe we should reuse zone paramater by passing a special zone id like
zone="*". There is already a special id ^, which means the first
container
zone.
I like this idea.
I''m using "^" a lot so at least for me it's a good concept.
Cheers
On Thu, Jan 5, 2012 at 2:40 PM, Lance Java<lance.j...@googlemail.com
wrote:
Correct me if I'm wrong but currently, if you want an eventlink to
use
ajax, you must provide a "zone" parameter. This may have been fine in
early
versions of tapestry 5 but there are now circumstances where we want
an
eventlink to be done via XHR but shouldn't need to specify a zone in
the
tml. These include:
1. MultiZoneUpdate where the zone(s) are determined in the event
handler
2. AjaxResponseRenderer where zone updates and javascript execs can
be
invoked in the event handler
As a suggestion, eventlink could have a new boolean parameter for
ajax
eg<t:eventlink event="foo" ajax="true" />
Should I raise a JIRA for this?
--
Best regards,
Igor Drobiazko
http://tapestry5.de
http://twitter.com/drobiazko
--
*Regards,*
*Muhammad Gelbana
Java Developer*
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org