diff options
| author | http://kerravonsen.dreamwidth.org/ <http://kerravonsen.dreamwidth.org/@web> | 2010-07-29 02:47:26 +0000 |
|---|---|---|
| committer | Joey Hess <joey@finch.kitenet.net> | 2010-07-29 02:47:26 +0000 |
| commit | 4bc3839df8fa47affc114a37ce862e3171d3e922 (patch) | |
| tree | 34d54aa32515fa6c032d7a885b4322467d82946f | |
| parent | ccf80cfa8a012325c375295630898267a5d28d64 (diff) | |
what approach to take for pagination?
| -rw-r--r-- | doc/forum/report_pagination.mdwn | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/forum/report_pagination.mdwn b/doc/forum/report_pagination.mdwn new file mode 100644 index 000000000..d609fd502 --- /dev/null +++ b/doc/forum/report_pagination.mdwn @@ -0,0 +1,11 @@ +I am thinking of adding pagination to the [[plugins/contrib/report]] plugin, but I'm not sure which is the best approach to take. (By "pagination" I mean breaking up a report into multiple pages with N entries per page.) + +Approaches: + +1. generate additional HTML files on the fly which are placed in the sub-directory for the page the report is on. These are not "pages", they are not under revision control, they aren't in the %pagesources hash etc. But using the `will_render` mechanism assures that they will be removed when they are no longer needed. + +2. create new pages which each have a report directive which shows a subset of the full result; add them to revision control, treat them as full pages. Problems with this are: (a) trying to figure out when to create these new pages and when not to, (b) whether or not these pages can be deleted automatically. + +3. some other approach I haven't thought of. + +I'm afraid that whatever approach I take, it will end up being a kludge. |