Author: mschulte
Date: Wed Mar 26 12:02:51 2008
New Revision: 641485
URL: http://svn.apache.org/viewvc?rev=641485&view=rev
Log:
fixes TAPESTRY-2266: Incorrect EventListener documentation for intercepting
Javascript functions
Modified:
tapestry/tapestry4/trunk/src/site/apt/ajax/eventlistener.apt
Modified: tapestry/tapestry4/trunk/src/site/apt/ajax/eventlistener.apt
URL:
http://svn.apache.org/viewvc/tapestry/tapestry4/trunk/src/site/apt/ajax/eventlistener.apt?rev=641485&r1=641484&r2=641485&view=diff
==============================================================================
--- tapestry/tapestry4/trunk/src/site/apt/ajax/eventlistener.apt (original)
+++ tapestry/tapestry4/trunk/src/site/apt/ajax/eventlistener.apt Wed Mar 26
12:02:51 2008
@@ -128,12 +128,28 @@
of the answer like that:
+-----------------------------------------------------------------------
[EMAIL PROTECTED](events="trigger", targets="triggerable", elements="element")
[EMAIL PROTECTED](events="trigger", targets="triggerable")
public void onTriggered( BrowserEvent event )
{
doSomething(
event.getMethodArguments().getJSONObject(0).getInt("theAnswer") );
}
+-----------------------------------------------------------------------
+
+ The following Javascript snippet shows how <<<trigger()>>> could be defined:
+
++-----------------------------------------------------------------------
+<div jwcid="[EMAIL PROTECTED]"> ... </div>
+
+<script type="text/javascript">
+ var triggerable = document.getElementById('triggerable');
+ triggerable.trigger = function(params) {
+ alert('calling server with answer ' + params.theAnswer);
+ }
+</script>
++-----------------------------------------------------------------------
+
+ In fact, the function <<<trigger>>> is not even required to exist, which
comes in handy
+ if its only purpose would have been being intercepted at the server-side.
** Submitting forms when an event happens, and bypass client validation while
you're at it
