Changes for page Development-WODisplayGroup
Last modified by Pascal Robert on 2010/09/19 10:30
From version 7.1
edited by David Holt
on 2007/12/13 14:48
on 2007/12/13 14:48
Change comment:
There is no comment for this version
To version 8.1
edited by David Holt
on 2007/12/13 14:50
on 2007/12/13 14:50
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -31,7 +31,7 @@ 31 31 32 32 {{/warning}} 33 33 34 -* If you would like to page your results, a convenient way to do so is to set the "Entities per batch" you would like to display on your page. If you think of results pages for Google searches or flickr photo pages, a good rule of thumb is about 10 items per page. You can use the WOBatchNavigation component to paginate the results for you. 34 +* If you would like to page your results, a convenient way to do so is to set the "Entities per batch" you would like to display on your page. If you think of results pages for Google searches or flickr photo pages, a good rule of thumb is about 10 items per page. You can use the WOBatchNavigationBar component to paginate the results for you. 35 35 * You can set how you want your query to the database to be processed in the display group fetch. Do you want the text item at the start of the data (prefix), somewhere in the data (contains) or ending the data (suffix). 36 36 * The "Fetches on Load" tells the component whether the values for the entity to be displayed should be fetched from the database when the page is initially created or not. 37 37 * The sorting pull down allows you to tell the display group which attribute of the entity to sort on when the entities are displayed in a list. Below the attribute you select, you can choose whether you want the attribute to be sorted in ascending or descending order, or whether it should be left unsorted.