From: Sven Schöling Date: Fri, 23 Nov 2012 11:47:52 +0000 (+0100) Subject: Bessere Doku für das Zwischenformat des Paginated Helpers X-Git-Tag: release-3.0.0beta2~5 X-Git-Url: http://wagnertech.de/git?a=commitdiff_plain;h=e3815e78a82ba3abc12fc0daf61cb910186025ec;p=kivitendo-erp.git Bessere Doku für das Zwischenformat des Paginated Helpers --- diff --git a/SL/DB/Helper/Paginated.pm b/SL/DB/Helper/Paginated.pm index 27daffedd..07e5b5e9c 100644 --- a/SL/DB/Helper/Paginated.pm +++ b/SL/DB/Helper/Paginated.pm @@ -114,7 +114,7 @@ In the template: Paginate will prepare information to be used for paginating, change the given args to use them, and return a data structure containing information for later -display. +display. See L for information how the return is formatted. C needs to contain a reference to a hash, which will be used as an argument for C. After C the keys C and C @@ -129,6 +129,52 @@ Manager will be used. =back +=head1 STRUCTURE OF PAGES + +The returned hashref will have the following structure: + + { per_page => 20, # how many entries per page + max => 5, # number of the last page + cur => 2, # number of the current page + common => [ # an array of hashes for each page + ..., + { active => 1, # set if this is the active page + page => 2, # the string to display for this page + visible => 1, # should this be displayed in the paginating controls + }, + ... + ] + } + +You may assume that C is sanitized to be within 1..C. + +The common list is kept arbitrary by design, so that the algorithm to display +the paginating controls can be changed by solely changing the +C algorithm. If you need different glyphs for the pages or +different boundaries, translate the C entry for the page. + +The initial algorithm will show the following pages: + +=over 4 + +=item * + +1, 2, 3 + +=item * + +Last page + +=item * + +Current page +/- 5 pages + +=item * + +Current page +/- 10, 50, 100, 500, 1000, 5000 + +=back + =head1 TEMPLATE HELPERS =over 4