Widget Events"

From Documentation
m
Line 5: Line 5:
 
A widget event is the widget-level event (<javadoc directory="jsdoc">zk.Event</javadoc>).  
 
A widget event is the widget-level event (<javadoc directory="jsdoc">zk.Event</javadoc>).  
  
Like <javadoc>org.zkoss.zk.event.Event</javadoc> at the server side, the widget event can be any thing, and can be triggered by a widget or an application to notify a widget-level or application-level event, such as a window has been moved.
+
Like <javadoc>org.zkoss.zk.event.Event</javadoc> at the server side, the widget event can be anything, and can be triggered by a widget or an application to notify a widget-level or application-level event, such as a window has been moved.
  
 
In additions, ZK Client Engine intercepts most DOM events and encapsulate them into widgets events, such that it is easier and more efficient for component developers to handle events at widget-level (rather than DOM-level, <javadoc directory="jsdoc">jq.Event</javadoc>).
 
In additions, ZK Client Engine intercepts most DOM events and encapsulate them into widgets events, such that it is easier and more efficient for component developers to handle events at widget-level (rather than DOM-level, <javadoc directory="jsdoc">jq.Event</javadoc>).
  
 
=Event Listening for Application Developers=
 
=Event Listening for Application Developers=
To listen a widget event, you could invoke <javadoc method="listen(_global_.Map, int)" directory="jsdoc">zk.Widget</javadoc>.
+
 
 +
To listen a widget event, you could invoke <javadoc method="listen(_global_.Map, int)" directory="jsdoc">zk.Widget</javadoc> to listen the widget event you want. However, <javadoc method="listen(_global_.Map, int)" directory="jsdoc">zk.Widget</javadoc> is designed for applications to listen events at the client. For component development, the method overriding is suggested as described in the following subsections.
 +
 
 +
The signature of an event listener is as follows.
 +
 
 +
<source lang="javascript">
 +
function (event) { //an instance of zk.Event
 +
}
 +
</source>
  
 
=Event Listening for Component Developers=
 
=Event Listening for Component Developers=

Revision as of 08:47, 20 December 2010


A widget event is the widget-level event (Event).

Like Event at the server side, the widget event can be anything, and can be triggered by a widget or an application to notify a widget-level or application-level event, such as a window has been moved.

In additions, ZK Client Engine intercepts most DOM events and encapsulate them into widgets events, such that it is easier and more efficient for component developers to handle events at widget-level (rather than DOM-level, Event).

Event Listening for Application Developers

To listen a widget event, you could invoke Widget.listen(Map, int) to listen the widget event you want. However, Widget.listen(Map, int) is designed for applications to listen events at the client. For component development, the method overriding is suggested as described in the following subsections.

The signature of an event listener is as follows.

function (event) { //an instance of zk.Event
}

Event Listening for Component Developers

Event Propgation

A widget event will be propagated to the parent widget, parent's parent and so on, until stopped (Event.stop(Map)). Then, if the event is required by the server, it will be sent to the server, and converted to an instance of AuRequest at the server[1].


  1. For more information, please refer to the AU Requests section.

Event Firing

To fire a widget event, you could invoke Widget.fire(String, Object, Map, int) or Widget.fireX(Event, int).

Then, the listeners registered with Widget.listen(Map, int) will be invoked one-by-one. Then, it will be sent to the server, if an event listener has been registered at the server or it is an import event[1].

A client-side event listener could stop the sending of a widget event to the server by invoking Event.stop(Map) with {au:true}, such as

evt.stop({au: true});

  1. For more information, please refer to the AU Requests section.

Version History

Last Update : 2010/12/20


Version Date Content
     



Last Update : 2010/12/20

Copyright © Potix Corporation. This article is licensed under GNU Free Documentation License.