Paging"

From Documentation
m (Created page with 'init')
 
 
(49 intermediate revisions by 10 users not shown)
Line 1: Line 1:
init
+
{{ZKComponentReferencePageHeader}}
 +
 
 +
= Paging =
 +
 
 +
*Demonstration: [http://www.zkoss.org/zkdemo/grid/paging Paging (with Grid)], [http://www.zkoss.org/zkdemo/listbox/paging Paging (with Listbox)], [http://www.zkoss.org/zkdemo/tree/paging Paging (with Tree)]
 +
*Java API: <javadoc>org.zkoss.zul.Paging</javadoc>
 +
*JavaScript API: <javadoc directory="jsdoc">zul.mesh.Paging</javadoc>
 +
*Style Guide: [[ZK_Style_Guide/XUL_Component_Specification/Paging| Paging]]
 +
 
 +
= Employment/Purpose =
 +
 
 +
A <code>paging</code> component is used with another component to separate long content into multiple pages. If a component has long content to display, you could separate them into pages, and then use a paging component as a controller to allow the user decide which page to display.
 +
 
 +
The [[ZK Component Reference/Data/Listbox|listbox]], [[ZK Component Reference/Data/Grid|grid]] and [[ZK Component Reference/Data/Tree|tree]] components support the paging intrinsically, so you don't need to specify a paging component explicitly. In other words, they will instantiate and manage a paging component automatically if the paging mold is specified. Of course, you could specify an external paging component, if you want to have different visual layout, or to control multiple listboxes, grids and/or trees with one single paging component.
 +
 
 +
= Example =
 +
 
 +
For example, suppose you have 100 items and prefer to show 20 items at a time, then you can use the paging components as follows.
 +
 
 +
<source lang="xml" >
 +
<paging totalSize="100" pageSize="20"/>
 +
</source>
 +
 
 +
[[Image:paging_mold_default.png ]]
 +
 
 +
When a user clicks on the hyperlinks, the <code>onPaging</code> event is sent with an instance of <javadoc>org.zkoss.zul.event.PagingEvent</javadoc> to the paging component. To decide which portion of your 100 items are visible, you should add a listener to the paging component. Please note that the code below is pseudo code. For real examples, please refer to [[#Use_Cases|User Cases]] below.
 +
 
 +
<source lang="xml" >
 +
<zk>
 +
<div id="content"/> <!-- the long content is displayed here -->
 +
<paging id="paging" />
 +
 +
<zscript>
 +
List result = new SearchEngine().find("ZK");
 +
//assume SearchEngine.find() will return a list of items.
 +
 +
paging.setTotalSize(result.size());
 +
paging.addEventListener("onPaging", new org.zkoss.zk.ui.event.EventListener() {
 +
public void onEvent(Event event) {
 +
int pgno = event.getPaginal().getActivePage();
 +
int ofs = pgno * event.getPaginal().getPageSize();
 +
 
 +
new Viewer().redraw(content,
 +
result, ofs, ofs + event.getPaginal().getPageSize() - 1);
 +
//assume redraw(Div content, List result, int b, int e) will display
 +
//the result to the content component from the b-th item to the e-th item
 +
}
 +
}
 +
);
 +
</zscript>
 +
</zk>
 +
</source>
 +
 
 +
=Properties=
 +
== Disabled ==
 +
{{versionSince| 8.0.3}}
 +
 
 +
<javadoc method="setDisabled(boolean)">org.zkoss.zul.Paging</javadoc> is used to disable the paging component. It can block the user from navigating through the pagination. For example,
 +
 
 +
<source lang="xml">
 +
<paging pageSize="2" disabled="true"/>
 +
</source>
 +
 
 +
 
 +
== PageIncrement ==
 +
Default: 10 (desktop), 5 (mobile)
 +
Under <code>os</code> mold, the component renders a list of paging anchors for users to jump to the specific page:
 +
[[File:PagingAnchor.jpg]]
 +
 
 +
This attribute determines the max number of rendered paging anchors.
 +
 
 +
=Limitation=
 +
Paging can not apply [[ZK Developer's Reference/Performance Tips/Specify Stubonly for Client-only Components | stubonly]] at the same time. For example,
 +
<source lang="xml" >
 +
<listbox mold="paging" pageSize="1" >
 +
<listitem >
 +
<listcell stubonly="true"/>
 +
</listitem>
 +
<listitem>
 +
<listcell />
 +
</listitem>
 +
</listbox>
 +
</source>
 +
Although paging will [[ZK_Developer's_Reference/UI_Composing/Component-based_UI#Invalidate_a_Component|invalidate]] <code>listbox</code> and its children, <code>stubonly</code> needs the referred widget in client side which is detached during paging and throws mounting error.
 +
 
 +
=Supported Events=
 +
 
 +
{| class='wikitable' | width="100%"
 +
! <center>Name</center>
 +
! <center>Event Type</center>
 +
|-
 +
| <center><code>onPaging</code></center>
 +
|  '''Event:''' <javadoc>org.zkoss.zul.event.PagingEvent</javadoc>
 +
 
 +
Notifies one of the pages of a multi-page component is selected by the user.
 +
 
 +
|}
 +
 
 +
*Inherited Supported Events: [[ZK_Component_Reference/Base_Components/XulElement#Supported_Events | XulElement]]
 +
 
 +
=Supported Molds=
 +
Available molds of a component are defined in lang.xml embedded in zul.jar.
 +
{| class='wikitable' | width="100%"
 +
! <center>Name</center>
 +
! <center>Snapshot</center>
 +
|-
 +
| <center>default</center>
 +
|[[Image:paging_mold_default.png ]]
 +
|-
 +
| <center>os</center>
 +
|[[Image:paging_mold_os.png ]]
 +
|}
 +
 
 +
=Supported Children=
 +
 
 +
*NONE
 +
 
 +
=Use Cases=
 +
 
 +
{| class='wikitable' | width="100%"
 +
! Version !! Description !! Example Location
 +
|-
 +
| 3.6
 +
| Small talks
 +
|
 +
* [[Small Talks/2009/July/Handling huge data using ZK|Handling huge data using ZK]]
 +
* [[Small_Talks/2009/May/Paging_Sorting_with_a_filter_object |Paging Sorting with a filter object]]
 +
* [[Small_Talks/2008/June/Use_Load-On-Demand_to_Handle_Huge_Data|Use Load-On-Demand to Handle Huge Data]]
 +
|}
 +
 
 +
=Version History=
 +
{{LastUpdated}}
 +
 
 +
{| class='wikitable' | width="100%"
 +
! Version !! Date !! Content
 +
|-
 +
| &nbsp;
 +
| &nbsp;
 +
| &nbsp;
 +
|}
 +
 
 +
{{ZKComponentReferencePageFooter}}

Latest revision as of 04:42, 25 January 2022

Paging

Employment/Purpose

A paging component is used with another component to separate long content into multiple pages. If a component has long content to display, you could separate them into pages, and then use a paging component as a controller to allow the user decide which page to display.

The listbox, grid and tree components support the paging intrinsically, so you don't need to specify a paging component explicitly. In other words, they will instantiate and manage a paging component automatically if the paging mold is specified. Of course, you could specify an external paging component, if you want to have different visual layout, or to control multiple listboxes, grids and/or trees with one single paging component.

Example

For example, suppose you have 100 items and prefer to show 20 items at a time, then you can use the paging components as follows.

<paging totalSize="100" pageSize="20"/>

Paging mold default.png

When a user clicks on the hyperlinks, the onPaging event is sent with an instance of PagingEvent to the paging component. To decide which portion of your 100 items are visible, you should add a listener to the paging component. Please note that the code below is pseudo code. For real examples, please refer to User Cases below.

<zk>
	<div id="content"/> <!-- the long content is displayed here -->
	<paging id="paging" />
	
	<zscript>
	List result = new SearchEngine().find("ZK");
	//assume SearchEngine.find() will return a list of items.
	
	paging.setTotalSize(result.size());
	paging.addEventListener("onPaging", new org.zkoss.zk.ui.event.EventListener() {
		public void onEvent(Event event) {
			int pgno = event.getPaginal().getActivePage();
			int ofs = pgno * event.getPaginal().getPageSize();

			new Viewer().redraw(content,
				result, ofs, ofs + event.getPaginal().getPageSize() - 1);
			//assume redraw(Div content, List result, int b, int e) will display
			//the result to the content component from the b-th item to the e-th item
			}
		}
	);
	</zscript>
</zk>

Properties

Disabled

Since 8.0.3

Paging.setDisabled(boolean) is used to disable the paging component. It can block the user from navigating through the pagination. For example,

<paging pageSize="2" disabled="true"/>


PageIncrement

Default: 10 (desktop), 5 (mobile)

Under os mold, the component renders a list of paging anchors for users to jump to the specific page: PagingAnchor.jpg

This attribute determines the max number of rendered paging anchors.

Limitation

Paging can not apply stubonly at the same time. For example,

<listbox mold="paging" pageSize="1" >
	<listitem >
		<listcell stubonly="true"/>
	</listitem>
	<listitem>
		<listcell />
	</listitem>
</listbox>

Although paging will invalidate listbox and its children, stubonly needs the referred widget in client side which is detached during paging and throws mounting error.

Supported Events

Name
Event Type
onPaging
Event: PagingEvent

Notifies one of the pages of a multi-page component is selected by the user.

Supported Molds

Available molds of a component are defined in lang.xml embedded in zul.jar.

Name
Snapshot
default
Paging mold default.png
os
Paging mold os.png

Supported Children

*NONE

Use Cases

Version Description Example Location
3.6 Small talks

Version History

Last Update : 2022/01/25


Version Date Content
     



Last Update : 2022/01/25

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