Controller"
From Documentation
m (→Overview) |
|||
| Line 6: | Line 6: | ||
For a simple UI, there is no need of controller. For example, the data of a <javadoc>org.zkoss.zul.Listbox</javadoc> could be abstracted by implementing <javadoc type="interface">org.zkoss.zul.ListModel</javadoc>. | For a simple UI, there is no need of controller. For example, the data of a <javadoc>org.zkoss.zul.Listbox</javadoc> could be abstracted by implementing <javadoc type="interface">org.zkoss.zul.ListModel</javadoc>. | ||
| − | For typical database access, the glue logic (i.e., control) can be handled by a generic feature called [[ZK Developer's Reference/Data Binding|Data Binding]]. In other words, the read and | + | For typical database access, the glue logic (i.e., control) can be handled by a generic feature called [[ZK Developer's Reference/Data Binding|Data Binding]]. In other words, the create, read, update and delete operations (CRUD) can be handled automatically by a generic Data Binding, and you don't need to write the glue logic at all. |
In this section we will discuss how to implement a custom controller (which is called a composer in ZK terminology). | In this section we will discuss how to implement a custom controller (which is called a composer in ZK terminology). | ||
Revision as of 01:50, 29 December 2010
Overview
The controller is a Java program that is used to glue UI (view) and Data (model) together.
For a simple UI, there is no need of controller. For example, the data of a Listbox could be abstracted by implementing ListModel.
For typical database access, the glue logic (i.e., control) can be handled by a generic feature called Data Binding. In other words, the create, read, update and delete operations (CRUD) can be handled automatically by a generic Data Binding, and you don't need to write the glue logic at all.
In this section we will discuss how to implement a custom controller (which is called a composer in ZK terminology).
Version History
| Version | Date | Content |
|---|---|---|