Grid Template"

From Documentation
m (replace tt with code (via JWB))
m
 
(One intermediate revision by one other user not shown)
Line 20: Line 20:
 
</source>
 
</source>
  
where <code>books</code> is assumed as an instance of <javadoc type="interface">org.zkoss.zul.ListModel</javadoc> that contains a list of the Book instances while each Book instances has at least three getter methods: <code>getIsbn</code>, <code>getName</code> and <code>getDescription</code>.
+
where <code>books</code> is assumed as an instance of <javadoc type="interface">org.zkoss.zul.ListModel</javadoc> that contains a list of the Book instances while each Book instance has at least three getter methods: <code>getIsbn</code>, <code>getName</code> and <code>getDescription</code>.
  
 
Notice that the template named <code>model</code> must be associated with the grid, i.e., it must be a direct child element of the grid element as shown above. A common mistake is to put it under the rows element. Remember the template is a ZUML fragment telling the grid how to render a row, and the template itself is not a component.
 
Notice that the template named <code>model</code> must be associated with the grid, i.e., it must be a direct child element of the grid element as shown above. A common mistake is to put it under the rows element. Remember the template is a ZUML fragment telling the grid how to render a row, and the template itself is not a component.
Line 42: Line 42:
 
</source>
 
</source>
  
* Note the ''groupingInfo'' is used to get the information of the grouping data. Please refer to <javadoc>org.zkoss.zul.ext.GroupingInfo</javadoc>
+
* Note the ''groupingInfo'' is used to get the information of the grouping data. Please refer to <javadoc>org.zkoss.zul.ext.GroupingInfo</javadoc>.
  
 
=Version History=
 
=Version History=
{{LastUpdated}}
+
 
 
{| class='wikitable' | width="100%"
 
{| class='wikitable' | width="100%"
 
! Version !! Date !! Content
 
! Version !! Date !! Content

Latest revision as of 02:43, 30 January 2024

Similar to Listbox, you can define a customer rendering with a template for a grid:

<grid model="${books}">
	<columns>
		<column label="ISBN" sort="auto"/>
		<column label="Name" sort="auto"/>
		<column label="Description"/>
	</columns>
	<template name="model">
		<row>
			<label value="${each.isbn}"/>
			<label value="${each.name}"/>
			<label value="${each.description}"/>
		</row>
	</template>
</grid>

where books is assumed as an instance of ListModel that contains a list of the Book instances while each Book instance has at least three getter methods: getIsbn, getName and getDescription.

Notice that the template named model must be associated with the grid, i.e., it must be a direct child element of the grid element as shown above. A common mistake is to put it under the rows element. Remember the template is a ZUML fragment telling the grid how to render a row, and the template itself is not a component.

Template for GroupsModel

When used with GroupsModel, grids will use the template called model:grouping for rendering the grouping object. If it is not defined, it will look for the template called model instead (i.e., the same template is used for rendering the grouping and non-grouping objects).

<grid mode="${fooGroupsModel}">
   <template name="model:group">
      <group open="${groupingInfo.open}">....</group>
   </template>
   <template name="model">
      <row>....</row>
   </template>
   <template name="model:groupfoot">
      <groupfoot>....</groupfoot>
   </template>
<grid>
  • Note the groupingInfo is used to get the information of the grouping data. Please refer to GroupingInfo.

Version History

Version Date Content
6.0.0 July 2011 The template feature was introduced.
6.0.0 January 2012 The GroupingInfo statement was introduced.



Last Update : 2024/01/30

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