Client-side UI Composing"

From Documentation
m
m
Line 8: Line 8:
 
* For information about customizing client-side widget's behavior, please refer to [[ZK Client-side Reference/General Control/Widget Customization|ZK Client-side Reference: Widget Customization]].
 
* For information about customizing client-side widget's behavior, please refer to [[ZK Client-side Reference/General Control/Widget Customization|ZK Client-side Reference: Widget Customization]].
 
* For information about client-side markup language (iZUML), please refer to [[ZK Client-side Reference/General Control/iZUML|ZK Client-side Reference: iZUML]].
 
* For information about client-side markup language (iZUML), please refer to [[ZK Client-side Reference/General Control/iZUML|ZK Client-side Reference: iZUML]].
* For information about client-side event handling, please refer to [[ZK Client-side Reference/General Control/Event Listening:ZK Client-side Reference: Event Listening]]
+
* For information about client-side event handling, please refer to [[ZK Client-side Reference/General Control/Event Listening|ZK Client-side Reference: Event Listening]]
  
 
=Version History=
 
=Version History=

Revision as of 09:15, 10 December 2010


Client-side UI Composing


Though optional, you could have the total control of the client's functionality without the assistance of server-side code. Generally, you don't need to do it. You don't need to know how ZK Client Engine and client-side widgets communicate with the server. Their states are synchronized automatically by ZK. However, you could control it if necessary. It is the so-called Server-client fusion.

The rule of thumb is you should handle events and manipulate UI mostly, if not all, at the server, since it is more productive. Then, you could improve the responsiveness and visual effects, and/or reduce the load of the server by handling them at the client, when it is appropriate. Notice that JavaScript is readable by any user, so be careful not to expose sensitive data or business logic when migrating some code from server to client.

Version History

Last Update : 2010/12/10

Version Date Content
     



Last Update : 2010/12/10

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