Event Forwarding

From Documentation
Revision as of 09:41, 24 August 2010 by Tomyeh (talk | contribs) (Created page with '{{ZKComponentReferencePageHeader}} = Overview = For easy programming, ZK does not introduce any complex event flow. When an event is sent to a target component, only the event l…')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)


Overview

For easy programming, ZK does not introduce any complex event flow. When an event is sent to a target component, only the event listeners registered for the target component will be called. It is the application's job to forward an event to another component if required (by the application).

For example, you might have a menu item and a button to trigger the same action, say, opening a dialog, and then it is more convenient to have a single listener to open the dialog, and register the listener to the main window rather than register to both the menu item and the button.

Event Forwarding in Java

Forwarding an event is straightforward: just post or send the event again. However, there is a better way: composer. The composer can be the central place to handle the events. For example,

public class FooComposer extends GenericForwardComposer {
   public void onClick$menuitem() {
     openDialog();
   }
   public void onClick$button() {
     openDialog();
   }
   private void openDialog() {
     //whatever you want
   }
}

Event Forwarding in ZUL


Last Update : 2010/08/24

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