Click
  1. Click
  2. CLK-390

Separate the Paginator from the TableControl.

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.5 M1
    • Fix Version/s: 1.5 M3
    • Component/s: core
    • Labels:
      None

      Description

      Separate the Paginator (as a standalone and configurable Control) from the actual Table Control.

      This new "Paginator" Control should further remain the default in Table Control, so from the Table API perspective(actual user code) nothing would change - it would be backward compatible.

      This approach would have the following advantages over the actual approach:

      • it would allow to use it outside the Table (e.g. for normal dynamic pages, simple blogs, serch result pages, etc.).
      • it would allow to write other Paginator Controls (based on this one), e.g. the very popular DiggPaginator:
        http://woork.blogspot.com/2008/03/perfect-pagination-style-using-css.html
        or even totally different Paginators.
      • it would allow to use with the Table Control another Paginator than the default one (with a simple Table#setPaginator(diggPaginator), thus making TableControl even more flexible than it's now.

        Activity

        Hide
        Demetrios Kyriakis added a comment -

        +1 for such a feature/refactoring.

        That digg paginator looks very nice .

        I created a new request for that control - CLK-395
        http://www.avoka.com/jira/browse/CLK-395

        Show
        Demetrios Kyriakis added a comment - +1 for such a feature/refactoring. That digg paginator looks very nice . I created a new request for that control - CLK-395 http://www.avoka.com/jira/browse/CLK-395
        Hide
        Bob Schellink added a comment -

        Sounds useful.

        One feature not available in the above mentioned paginator, is ability to display the total amount of results.

        This helps when the search result is large (occurs when using a fulltext search engine such as Lucene) e.g:

        [prev] [1] [2] [3] [4] [5] ... [134434] [next]

        Show
        Bob Schellink added a comment - Sounds useful. One feature not available in the above mentioned paginator, is ability to display the total amount of results. This helps when the search result is large (occurs when using a fulltext search engine such as Lucene) e.g: [prev] [1] [2] [3] [4] [5] ... [134434] [next]

          People

          • Assignee:
            Malcolm Edgar
            Reporter:
            Gustav Weber
          • Votes:
            3 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development