This ViewHelper renders a Pagination of objects.

= Examples =

<f:widget.paginate objects="{blogs}" as="paginatedBlogs" configuration="{itemsPerPage: 5}"> // use {paginatedBlogs} as you used {blogs} before, most certainly inside // a <f:for> loop. </f:widget.paginate>

<f:widget.paginate objects="{blogs}" as="paginatedBlogs" configuration="{itemsPerPage: 5, insertAbove: true, insertBelow: false, maximumNumberOfLinks: 10}"> // This example will display at the maximum 10 links and tries to the settings // pagesBefore and pagesAfter into account to get the best result </f:widget.paginate> = Performance characteristics =

In the above example, it looks like {blogs} contains all Blog objects, thus you might wonder if all objects were fetched from the database. However, the blogs are NOT fetched from the database until you actually use them, so the paginate ViewHelper will adjust the query sent to the database and receive only the small subset of objects. So, there is no negative performance overhead in using the Paginate Widget.