cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simone Gianni (JIRA)" <>
Subject [jira] Commented: (COCOON-1877) [PATCH] Pageable Repeater
Date Fri, 28 Jul 2006 11:57:14 GMT
    [ ] 
Simone Gianni commented on COCOON-1877:

Committed this part, we tested it on a heavy hibernate backed application where we use repeaters
to output enormous (11000+items) lists, and works.

Things to do :
- A page number widget, with jump to page links
- Row insertion and deletion and harmonization with pages
- Disabling action buttons when we are in the first/last page

> [PATCH] Pageable Repeater
> -------------------------
>                 Key: COCOON-1877
>                 URL:
>             Project: Cocoon
>          Issue Type: New Feature
>          Components: Blocks: Forms
>            Reporter: Matthias Epheser
>         Attachments: repeater-pagination-2.patch, repeater-pagination.patch
> This patch provides simple pagination for the repeater widget using the binding.
> It consists of 3 main parts: It extends the repeater-definition to configure the pages,
adds a ChangePageAction for userinteraction and modifies the binding so savePage/loadPage
can be performed after the action is called.
> Speaking of a first demo with basic functionality there are some known issues and missing
> - We plan to use some internal "storage area" inside the binding that contains the updated
rows after a page-change. The real doSave() code should be called just once after the form
was submitted. This should provide better integration to scenarios where persistence frameworks
like hibernate are used.
> - The userinterface needs to be extended to features like next/first/last-page buttons
and the common "first 1 2 3 4 5 next" group of links to choose pages directly.
> - Filtering and Sorting of the rows would be nice and could maybe accomplished extending
the storage area implementation.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message