Implement ListModel and TreeModel"
m |
m |
||
| Line 3: | Line 3: | ||
The default implementation of models, such as <javadoc>org.zkoss.zul.ListModelList</javadoc> and <javadoc>org.zkoss.zul.DefaultTreeModel</javadoc> assumes all data are available in the memory. It is not practical if a model has a lot of data. For huge data, it is suggested to implement your own model by loading and caching only a portion of data at a time. | The default implementation of models, such as <javadoc>org.zkoss.zul.ListModelList</javadoc> and <javadoc>org.zkoss.zul.DefaultTreeModel</javadoc> assumes all data are available in the memory. It is not practical if a model has a lot of data. For huge data, it is suggested to implement your own model by loading and caching only a portion of data at a time. | ||
| − | To implement your own model, you could extend from <javadoc>org.zkoss.zul.AbstractListModel</javadoc>, <javadoc>org.zkoss.zul.AbstractGroupsModel<javadoc> and <javadoc>org.zkoss.zul.DefaultTreeModel</javadoc> as described in [[ZK Developer's Reference/MVC/Model|the Model section]]. To implement a model that supports sorting, you have to implement <javadoc type="interface">org.zkoss.zul.ListModelExt</javadoc> too. Each time an user requires sorting, <javadoc type="interface" method="sort(java.util.Comparator, boolean)">org.zkoss.zul.ListModelExt</javadoc> will be called and the implementation usually clears the cache and re-generate the SQL statement accordingly. | + | To implement your own model, you could extend from <javadoc>org.zkoss.zul.AbstractListModel</javadoc>, <javadoc>org.zkoss.zul.AbstractGroupsModel</javadoc> and <javadoc>org.zkoss.zul.DefaultTreeModel</javadoc> as described in [[ZK Developer's Reference/MVC/Model|the Model section]]. To implement a model that supports sorting, you have to implement <javadoc type="interface">org.zkoss.zul.ListModelExt</javadoc> too. Each time an user requires sorting, <javadoc type="interface" method="sort(java.util.Comparator, boolean)">org.zkoss.zul.ListModelExt</javadoc> will be called and the implementation usually clears the cache and re-generate the SQL statement accordingly. |
| + | |||
| + | Here is some pseudo code: | ||
| + | |||
For a real example, please refer to [[Small Talks/2009/July/Handling huge data using ZK|Small Talk: Handling huge data using ZK]]. | For a real example, please refer to [[Small Talks/2009/July/Handling huge data using ZK|Small Talk: Handling huge data using ZK]]. | ||
Revision as of 01:16, 10 March 2011
The default implementation of models, such as ListModelList and DefaultTreeModel assumes all data are available in the memory. It is not practical if a model has a lot of data. For huge data, it is suggested to implement your own model by loading and caching only a portion of data at a time.
To implement your own model, you could extend from AbstractListModel, AbstractGroupsModel and DefaultTreeModel as described in the Model section. To implement a model that supports sorting, you have to implement ListModelExt too. Each time an user requires sorting, ListModelExt.sort(Comparator, boolean) will be called and the implementation usually clears the cache and re-generate the SQL statement accordingly.
Here is some pseudo code:
For a real example, please refer to Small Talk: Handling huge data using ZK.
Version History
| Version | Date | Content |
|---|---|---|