Details

    • Type: Feature Request Feature Request
    • Status: Reopened
    • Priority: Critical Critical
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Search
    • Labels:
      None
    • Previous Issue Keys:
      SAK-9535, SRCH-31

      Description

      If I have a search that returns 70 results, it seems to want to show only a max of 6 page numbers (e.g. initially shows 1 2 3 4 5 6) and no more than 3 prior to the page that you've selected (e.g. when you're on 7 it shows 5 6 7).

      If so I think it would help to just increase those numbers, e.g. Google shows current page + next 10 + previous 10.

      Other UI changes that would help here are Previous and Next links (also like Google) as it's hard to click on the numbers, and also to unlink the current page so it's easier to see what page number you're on.

        Gliffy Diagrams

        1. pager.html
          5 kB
          Ian Boston
        2. pager.html
          4 kB
          Ian Boston
        1. search design.png
          92 kB
        2. search design 2.png
          94 kB
        3. search design 3.png
          93 kB

          Activity

          Hide
          Ian Boston added a comment -

          Hmmm, Sorry

          Not certain about the paging (next and previous), after testing here is why.

          If next does current page+1 and previous does current page -1 .....

          why do we remove previous when the first page in the list is page 0 and the current page is page 7 ?

          previous-1 would be 6 which is valid so the control is valid

          at the other end on page 93 (100 pages) we are not displaying next but page+1 is valid.

          If N = CP+1 and P = CP-1 then it makes no sense to hide them except when the page is 0 or 99 and
          the possition of next and previous is wrong and should be beside the current page.

          IMHO, next and previous are rapid scrolling controls that jump so that the current page becomes the page just beyond the last one shown.

          Soooo....

          I've uploaded a CP+-1 version (the second pager)

          Show
          Ian Boston added a comment - Hmmm, Sorry Not certain about the paging (next and previous), after testing here is why. If next does current page+1 and previous does current page -1 ..... why do we remove previous when the first page in the list is page 0 and the current page is page 7 ? previous-1 would be 6 which is valid so the control is valid at the other end on page 93 (100 pages) we are not displaying next but page+1 is valid. If N = CP+1 and P = CP-1 then it makes no sense to hide them except when the page is 0 or 99 and the possition of next and previous is wrong and should be beside the current page. IMHO, next and previous are rapid scrolling controls that jump so that the current page becomes the page just beyond the last one shown. Soooo.... I've uploaded a CP+-1 version (the second pager)
          Hide
          Ian Boston added a comment -

          New version with 2 pagers.

          The first one is a jump pager on the next and prev buttons

          The second one is a page+1 page -1

          Show
          Ian Boston added a comment - New version with 2 pagers. The first one is a jump pager on the next and prev buttons The second one is a page+1 page -1
          Hide
          Ian Boston added a comment -

          New pager versions uploaded

          Show
          Ian Boston added a comment - New pager versions uploaded
          Hide
          Stephen Marquard added a comment -

          Reopening as an unassigned FR because the UI is still in need of improvement.

          Show
          Stephen Marquard added a comment - Reopening as an unassigned FR because the UI is still in need of improvement.
          Hide
          David Horwitz added a comment -

          MAINT TEAM REVIEW: This feature request is currently unassigned and will be reviewed. In line with stated Jira practice http://confluence.sakaiproject.org/display/MGT/Sakai+Jira+Guidelines Feature requests that are not going to be implemented will be closed with a status of "wont fix". If you intend implementing this issue please ensure that its up to date and assigned correctly

          Show
          David Horwitz added a comment - MAINT TEAM REVIEW: This feature request is currently unassigned and will be reviewed. In line with stated Jira practice http://confluence.sakaiproject.org/display/MGT/Sakai+Jira+Guidelines Feature requests that are not going to be implemented will be closed with a status of "wont fix". If you intend implementing this issue please ensure that its up to date and assigned correctly

            People

            • Assignee:
              Unassigned
              Reporter:
              Stephen Marquard
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:

                Development