Chosenbox Renderer"
From Documentation
(Created page with "{{ZKDevelopersReferencePageHeader}} The implementation of a custom renderer for a Chosenbox (<javadoc type="interface">org.zkoss.zul.ItemRenderer</javadoc>) is straightforward<r...") |
|||
| Line 28: | Line 28: | ||
|- | |- | ||
| 6.0.1 | | 6.0.1 | ||
| − | | | + | | April 2012 |
| Chosenbox was introduced. | | Chosenbox was introduced. | ||
|} | |} | ||
{{ZKDevelopersReferencePageFooter}} | {{ZKDevelopersReferencePageFooter}} | ||
Revision as of 03:39, 5 April 2012
The implementation of a custom renderer for a Chosenbox (ItemRenderer) is straightforward[1]:
public class FooItemRenderer implements org.zkoss.zul.ItemRenderer {
public String render(Component owner, Object data, int index) throws Exception {
return data.toString(); //converting data to a string; it depends on your application's requirement
}
}
Then, if we have a list model (ListModel) called users, and an instance of a custom renderer called userRenderer, then we can put them together in a ZUML document as follows:
<chosenbox model="${users}" itemRenderer="${userRenderer}"/>
- ↑ For the concept about component, model and renderer, please refer to the Model-driven Display section.
Version History
| Version | Date | Content |
|---|---|---|
| 6.0.1 | April 2012 | Chosenbox was introduced. |