====== Paged View ====== //See also [[Fragments, Columns, Regions, Pages]], [[spec:css3-region-templates|CSS Region Templates]]// "Paged view" or "page view" as a term relates broadly to the kind of presentation where content is laid out in discrete pages and shown to user one page at a time (or several pages at a time). A wide variety of paged view situations require the same or similar support from the core layout engine -- primarily the ability to flow content into multiple containers, thus producing multiple boxes with fragments of content (see "[[Fragments, Columns, Regions, Pages]]"). Solutions differ in how the fragmentation functionality is invoked. The problems to be solved in implementing paged views revolve around encoding the design intent and UI behavior, both requiring novel approaches: design intent often derives from experience in print media, which must become adaptive to target multiple devices and resolutions. The UI of navigating pages on screen also doesn’t have an established tradition, although many implementations use similar concepts. This set of use cases shows some expected uses of paged views. The uses cases, analysis and proposals found here probably don’t correspond to a single specification. The goal here is to get a holistic view of each case, which will help to compare proposals and understand the relative importance of lower level problems. ====== Use Cases ====== ===== Page view in window or element ===== **Goal:** easy declarative way to create paged view, good behavior with default settings and default UI.