The navigation system in Windows Phone XAML apps is based on the Silverlight for the browser navigation model. The navigation class model looks a little different in the phone SDK however. Rather than Silverlight Frame
and Page
controls, Windows Phone apps use the subclasses PhoneApplicationFrame
and the PhoneApplicationPage
(see Figure 3.4).
Note
Frame
and Page
must not be used directly in your app. They are prohibited because of underlying differences in the way the run-time environment interacts with the OS within the constrained environment of the phone.
Page navigation in Windows Phone works in much the same way as page navigation in a web browser. PhoneApplicationFrame
is analogous to the web browser, coordinating page transitions within your app.
Figure 3.5 depicts the display elements of a Windows Phone app.
The PhoneApplicationFrame
is the host for PhoneApplicationPages
and reserves space for the system tray and the application bar. The PhoneApplicationPage
consumes all remaining space after the system tray and the application bar.
Note
There can be only one PhoneApplicationFrame
for an application. Attempting to place a PhoneApplicationFrame
within a PhoneApplicationPage
causes the content to become infinitely nested at runtime because the page will be forced inside the frame, the frame inside the page, and so on.
18.116.37.62