DOM Events"

From Documentation
Line 5: Line 5:
 
A DOM event (<javadoc directory="jsdoc">jq.Event</javadoc>) is the DOM-level event that is usually triggered by the browser. It is usually listened by the implementation of a widget, rather than the client application.
 
A DOM event (<javadoc directory="jsdoc">jq.Event</javadoc>) is the DOM-level event that is usually triggered by the browser. It is usually listened by the implementation of a widget, rather than the client application.
  
Since ZK Client Engine intercepts most DOM events and encapsulate them into the widget events, it is suggested to listen the widget events, if possible, for better performance (by overriding the corresponding methods, such as <javadoc method="doClick_(zk.Event)" directory="jsdoc">zk.Widget</javadoc>). For more information, please refer to [[ZK Client-side Reference/Notifications/Widget Events|the previous section]].  
+
Since ZK Client Engine can intercepts most DOM events and encapsulate them into the widget events, it is suggested to listen the widget events, if possible, for better performance (by overriding the corresponding methods, such as <javadoc method="doClick_(zk.Event)" directory="jsdoc">zk.Widget</javadoc>). For more information, please refer to [[ZK Client-side Reference/Notifications/Widget Events|the previous section]].  
  
 
= How to Listen and Unlisten =
 
= How to Listen and Unlisten =

Revision as of 08:20, 18 August 2011


A DOM event (Event) is the DOM-level event that is usually triggered by the browser. It is usually listened by the implementation of a widget, rather than the client application.

Since ZK Client Engine can intercepts most DOM events and encapsulate them into the widget events, it is suggested to listen the widget events, if possible, for better performance (by overriding the corresponding methods, such as Widget.doClick_(Event)). For more information, please refer to the previous section.

How to Listen and Unlisten

There are two different approaches to listen a DOM event: Widget.domListen_(DOMElement, String, Object) and jQuery (jq).

Use domListen_ and domUnlisten_

Widget.domListen_(DOMElement, String, Object) registers a DOM-level event listener. The registration shall be done when a widget is bound to DOM elements, i.e., when Widget.bind_(Desktop, Skipper, Array) is called. It is important to un-register by use of Widget.domUnlisten_(DOMElement, String, Object) when a widget is un-bound from DOM elements, i.e., when Widget.unbind_(Skipper, Array) is called. For example,

bind_: function () {
    this.$supers('bind_', arguments);
    this.domListen_(this.getNode(), "onChange");
},
unbind_: function () {
    this.domUnlisten_(this.node, "onChange");
    this.$supers('unbind_', arguments);
},
_doChange: function (evt) { //event listener
    //evt is an instance of jq.Event
},

Unlike jQuery's event listener (jq), Widget.domListen_(DOMElement, String, Object) will be ignored if the widget is under the control of ZK Weaver (a WYSIWYG editor), i.e., in the so-called Design Mode. In most cases, a widget shall not register any event listener when it is under control of ZK Weaver to avoid any conflict.

Use jQuery

The use of jQuery (jq) is similar except using one of the event listening methods found jQuery.

bind_: function () {
    this.$supers('bind_', arguments);
    jq(this.$("form")).bind("reset", this.proxy(this._resetForm));
},
unbind_: function () {
    jq(this.$("form")).unbind("reset", this.proxy(this._resetForm));
    this.$supers('unbind_', arguments);
},
_resetForm: function (evt) { //event listener
   this.doSomething(); //this refers to the widget since this.proxy is used
},

where we use Object.proxy(Function) to proxy a function such that this will refer to the widget when the method is called. Also notice that the event name used with jQuery does not start with on.

Version History

Last Update : 2011/08/18


Version Date Content
     



Last Update : 2011/08/18

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