581
Comment:
|
3190
|
Deletions are marked like this. | Additions are marked like this. |
Line 4: | Line 4: |
Location within a series of screens continuing display of a set of content should be clearly communicated, and access provided to other pages in the stack. | |
Line 7: | Line 8: |
The many screens displayed serially for large amounts of content may be considered pages, as though they are part of a bound paper item. Page numbers, and a sense of the relative position within the total, are displayed. Tied to this display is a method to move between pages easily and quickly. Methods to jump further than the previous and next page are also usually offered. |
|
Line 10: | Line 16: |
Two basic variations exist: '''Widget-based''' - A section of the page is dedicated to the display and control of items concerning pagination. Very often, there are actually two of these, with the same or a similar widget repeating at the top and bottom. If not, the item must usually be anchored to a non-scrolling title bar, so it is always accessible. '''Organic''' - Natural displays are becoming more common now, especially on touch and pen devices. These simulate "machine-era" presentation methods to imply the same information as the widget view. The display methods and interaction is integral with the design of the entire page, and is not in a specific location. |
|
Line 13: | Line 24: |
Pagination controls should be presented organically, with all controls visible or immediately accessible, whenever possible. When needed, a larger control panel style of interface may be offered instead. It may be accessed by selecting the pagination display elements. basic forward back button fwd/back gestures jump a few fwd/back; as google when individual pages listed, will run out of room jump to first/last Jump to arbitrary page, usually by typing number. Some of the jump methods may also be possible with gestures, and actions such as press-and-hold on the page flip section. However, these are not yet consistent and well-defined, so cannot yet be considered patterns. |
|
Line 16: | Line 40: |
clicky ones... Gestural ones.... and especially the implication of page thickness... |
|
Line 19: | Line 46: |
Pagination controls can easily get out of hand. In any reasonably complex system, it is easy to find justification for every method of page control. Avoid this, and attempt to only include the minimum set needed, so they can be placed on the page and be easy to find and use. Realist representations of pages must accurately reflect the information. For example, if a stack of pages is shown to the side, to indicate that more are available, the relative number shown must be of a plausible size to represent the number of pages, and must change the indicated size as pages are flipped. |
Conventional display "page of page" (7 of 23), range of total. This one is the interactive version. You can click prev/next, to a range, to a page, etc. All options covered... ALSO try to integrate gesture (or key) flip as for eReader style. Fake page flips, as indicator there are more pages (show accurate stack of pages, so it works like a scrollbar for position sense) and to indicate you moved to a new page.
Problem
Location within a series of screens continuing display of a set of content should be clearly communicated, and access provided to other pages in the stack.
Solution
The many screens displayed serially for large amounts of content may be considered pages, as though they are part of a bound paper item.
Page numbers, and a sense of the relative position within the total, are displayed.
Tied to this display is a method to move between pages easily and quickly. Methods to jump further than the previous and next page are also usually offered.
Variations
Two basic variations exist:
Widget-based - A section of the page is dedicated to the display and control of items concerning pagination. Very often, there are actually two of these, with the same or a similar widget repeating at the top and bottom. If not, the item must usually be anchored to a non-scrolling title bar, so it is always accessible.
Organic - Natural displays are becoming more common now, especially on touch and pen devices. These simulate "machine-era" presentation methods to imply the same information as the widget view. The display methods and interaction is integral with the design of the entire page, and is not in a specific location.
Interaction Details
Pagination controls should be presented organically, with all controls visible or immediately accessible, whenever possible. When needed, a larger control panel style of interface may be offered instead. It may be accessed by selecting the pagination display elements.
basic forward back button
fwd/back gestures
jump a few fwd/back; as google when individual pages listed, will run out of room
jump to first/last
Jump to arbitrary page, usually by typing number.
Some of the jump methods may also be possible with gestures, and actions such as press-and-hold on the page flip section. However, these are not yet consistent and well-defined, so cannot yet be considered patterns.
Presentation Details
clicky ones...
Gestural ones.... and especially the implication of page thickness...
Antipatterns
Pagination controls can easily get out of hand. In any reasonably complex system, it is easy to find justification for every method of page control. Avoid this, and attempt to only include the minimum set needed, so they can be placed on the page and be easy to find and use.
Realist representations of pages must accurately reflect the information. For example, if a stack of pages is shown to the side, to indicate that more are available, the relative number shown must be of a plausible size to represent the number of pages, and must change the indicated size as pages are flipped.