DOM Events"
From Documentation
m (Created page with '{{ZKClient-sideReferencePageHeader}} =Version History= {{LastUpdated}} {| border='1px' | width="100%" ! Version !! Date !! Content |- | | | |} {{ZKClient-s…') |
m |
||
Line 1: | Line 1: | ||
{{ZKClient-sideReferencePageHeader}} | {{ZKClient-sideReferencePageHeader}} | ||
+ | |||
+ | __TOC__ | ||
+ | There are two kinds of events at the client side: widget events (<javadoc directory="jsdoc">zk.Event</javadoc>) and DOM events (<javadoc directory="jsdoc">jq.Event</javadoc>). | ||
+ | |||
+ | = Widget Events = | ||
+ | A widget event is the widget-level event that a widget can fire (<javadoc method="fire(_global_.String, zk.Object, _global_.Map, int)" directory="jsdoc">zk.Widget</javadoc>) and the client application can listen (<javadoc method="listen(_global_.Map, int)" directory="jsdoc">zk.Widget</javadoc>). Its role is similar to <javadoc>org.zkoss.zk.event.Event</javadoc> at the server side<ref>It is converted to an AU request (<javadoc type="interface">org.zkoss.zk.au.AuRequest</javadoc>) when arrives at the server. For more information, please refer to the [[ZK Client-side Reference/Communication/AU Requests|AU Requests]] section.</ref>. | ||
+ | |||
+ | = DOM Events = | ||
+ | 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. | ||
+ | |||
+ | == How to Listen and Unlisten == | ||
+ | == When to Listen and Unlisten == | ||
+ | <blockquote> | ||
+ | ---- | ||
+ | <references/> | ||
+ | </blockquote> | ||
=Version History= | =Version History= |
Revision as of 04:51, 20 December 2010
There are two kinds of events at the client side: widget events (Event) and DOM events (Event).
Widget Events
A widget event is the widget-level event that a widget can fire (Widget.fire(String, Object, Map, int)) and the client application can listen (Widget.listen(Map, int)). Its role is similar to Event at the server side[1].
DOM Events
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.
How to Listen and Unlisten
When to Listen and Unlisten
- ↑ It is converted to an AU request (AuRequest) when arrives at the server. For more information, please refer to the AU Requests section.
Version History
Version | Date | Content |
---|---|---|