- Enable popover panels
- Enable multipage
- Enable splitview
The demo is work-in-progress. Go here: Multiview Demo
D. Getting started
A multiview page is a regular JQM page. To make it a multiview page, just add the data-wrapper="true" attribute to your container page. Any header or footer added to this page will act as a global header/footer for all nested pages, while header/footer on the nested-page level are local.
If you just want to add popover panels to your page, drop them after the content section. For splitview or fullwidth panels, replace the content section with the respective panels.
- a panel can contain any number of nested pages (regular JQM pages)
- nested pages can have header/footer spanning panel width and being local elements vs. global header/footer defined on the wrapping page
- there are four supported panel types: (1) menu, (2) main and (3) fullwidth and (4) popover
- any number of popovers are possible, but only one menu, main and fullwidth panel per "wrapper-page"
- panels use data-id, while JQM pages use id, this ensures JQM doesn't mix them up
- for a panel to work the first page to show needs to be specified by assigning data-show="first" to a page inside each panel
2. Screen Modes
Multiview is using three screenmodes:
(1) FullWidth/Splitview-Mode with main section or menu/main section visible
(2) popover mode on smaller screens (with toggle button) are similar to the original plugin.
(3) Fullscreen mode for smaller displays. In this mode, everything that pops up (popovers or the menu in popover mode) becomes a fullscreen element layering on top of the actual page (sort of like a dialog).
All popovers share the same functionalities, including the menu in popover mode. Popover panels can be formatted via CSS to be any size and position. However, only one popover can currently be open at a time(!).
Setting up popovers requires a trigger button with the class of .toggle_popover and corresponding data-panel="panel_name" attribute.
The plugin adds a second navigation layer which fires on any link that includes a data-target="panel_name". This target tells JQM to not use regular transition from page to page. Instead a panel-transition is used, which can be either inside a panel (changepage inside panel A) or cross-panel (like changepage panel B fired from A). If no data-target is defined, normal JQM will handle the transition (easiest way to mess up things).
The plugin allows two types of "history".
By adding data-hash="crumbs" to a panel, the plugin adds a back-button on every transitioned-to-page. Clicking this button reverses the transition (also works across panels).
Adding data-hash="history" to a panel allows to use the browser or device back-button. This is done by panel-history-stacks, which the plugin initiates when a panel is created. As long as a panel is visible new entries are made to the respective stack on every pagechange with main/menu panels increasing together. On clicking the back button, the plugin checks for the highest panel history stack(s), picks the stack to be used and transitions to the last (non-yield) stack-entry. When all panel stacks are on the same level (this should be the basic setup), normal JQM takes over and does a regular hash-change based reverse transition. This is still WORK-IN-PROGRESS A possible panel history scenario might look like this:
6. Fullscreen Mode
This mode fires automatically below a threshold screen width (320px) or if any popover.height plus offset from top is larger than screen.avail-height. In Fullscreen Mode the following things change:
- buttons with class .iconpos-switcher-a/div are set to icon-only buttons to save space
- the popover formatting is dropped. Menu and popovers are set to fullscreen size
- Toggling a popover will open the popovers as a layer above the main-panel (maybe eventually make this a dialog)
- any fixed header/footers on main panel are unfixed, header/footer on popover remain fixed
- The main panel height (actual page height) is matched to the visible popovers height to enable device scrolling (user sees popover-panel, and scrolls main-panel behind). Once the panel is closed, the height is set back to its original value
Multiview uses the scrollview plugin, which will only be initiated on touch devices, while in splitview/fullscreen mode. In this case (should be tablets only) all popovers and the menu use scrollview, while the main section uses device scrolling.
On desktop all panels have regular scrollbars. In fullscreen mode only the main panel device-scrolls with its height being matched to any open popover (see above). The idea is to keep scrollview use to a minimum versus device scrolling and more importantly, to not end up with device scrolling and scrollview firing at the same time.
8. Fixed Elements and global header/footer
Multiview adds two new fixed elements:
.ui-element-fixed-top and .ui-fixed-element-bottom
These can be used to attach panels (or any other element) to a fixed header/footer. This way when scrolling on a page, the panels will be re-positioned together with the fixed header/footer. Otherwise they would be stuck at their set position which is scrolled out of view. Fixed elements will be hidden together with header/footer once scrolling starts. However, they do not re-appear automatically. The user has to click the toggle-button to make them show up again.
To setup a global header or footer, just position it outside the panel and inside the wrapper page. These elements will be used across all panel pages.
9. Autoshow, Centered Popovers and Switchable
The plugin offers some additional functionalities, among them:
- set data-autoshow="once" on a po tpover and it will show once when the page finishes loading (think login window for an application)
- give your popover a class of .ui-popover-center and the popover will be positioned center-screen
- if you want to toggle the menu in splitview mode, you can add the plugin option switchable:true, which will show the menu toggle button in splitview mode, too. Use the additional options to configure the button icon and whether to show the menu on load.
- by default, the menu button is inside the header. You can now move it to any element in the main section by adding a class of .ui-menu-button-flex to this element.
10. Context Loading
Specifying data-context="page_name" and data-context-panel="panel_name" on a link will trigger an additional (context-)changePage when this link is fired. For example calling a submenu in the menu panel could trigger a changepage in the main section to transition to a related page simultaneously. Context loading will also adds entries to the panel history, so clicking the back button twice will revert both transitions (still in wrong order).
11. Deep Linking
Deeplinks work for all pages that are in the wrapper page when it's loaded. For pages that are added programmatically or via AJAX, the plugin currently breaks. Will be changed to at least showing the main page, or solved by adding a sitemap in the plugin options, which specifies pages-not-on-board-on-load and which panels they should be in.