HTML and CSS Reference
In-Depth Information
the user's navigation history, letting you provide a better user experience as you merge new pages
into the existing layout.
Jumping to a different page
The benefit of using the native Windows Store navigation model is well illustrated by the diagram in
Figure 7-1.
FIGURE 7-1 Jumping from one page to another using the classic HTML hyperlink element.
After clicking the link (or some button), the user sees a completely different page. It is your
responsibility to ensure that the user experiences a strong feeling of continuity. You typically achieve
that by giving both pages the same layout, using a common color scheme, and fonts. In addition, you
should provide users with links to return to the previous page, since you won't get any browser-like
Back button automatically from the system.
Displaying a different page
The idea behind the Windows Store application navigation model is that the application consists
of a single main page and a number of page fragments . The main page contains the header, footer,
menus, and other shared parts of the user interface. In contrast, a page fragment just provides new
content to replace the content in the main page. In this way, all common parts of the UI remain
unchanged during navigation, so the user has the feeling of having changed only context, rather
than having jumped to an entirely new place. Figure 7-2 illustrates the Windows Store application
navigation model.
FIGURE 7-2 Displaying different content within the same container.
Search WWH ::

Custom Search