Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Section
Column
width65%

Excerpt

The Pager allows the user to browse through data by breaking up a set of results into a series of pages.

What problem are we solving?

Allow users to break up long lists of items into separate pages.  They should be able to decide if they want paging and how many per page.

Currently in Sakai

:

Sakai has page navigation called "List Navigator UI Component" in the Sakai style guide.  The default for how many items to show on a page varies.  How many makes sense depends on context, how many total items, what type of items, etc.  The idea here is to make this navigator remember the users last setting (across sessions).  That way they set if for what makes sense given the current situation and it is persistent.  As things change for them they simply change the setting to meet current needs and again it's persistent until they need to change it again.  Currently this is a "one size fits all" default and many users have to change it every time they visit a particular page.

Who are we designing for?

Persona goes here.

Column
width35%
Panel
borderColor#566b30
bgColor#fff
titleBGColor#D3E3C4
titleOn this Page
borderStylesolid
Table of Contents
minLevel2

...

Section
Column
width50%
Panel
bgColorwhite
titleBGColor#c1b7c3
titleInteraction Design
borderStylesolid

Wireframes

Context storyboards

Design pattern

  • Nothing yet.

Functional requirements

User testing

Story cards

User Modeling

  • links to relevant Personas used

Accessibility

  • Nothing yet.
Column
width50%
Panel
bgColorwhite
titleBGColor#c1b7c3
titleTechnical Information
borderStylesolid

API

  • links to API documentation. Use excerpts if possible.Pager API

Integration

  • links to integration content. Use excerpts if possible.

Demos

  • links to usable demos and implementations.

Testing

  • nothing yet.

What needs are we meeting?

...