Base class that all Pages in the application should inherit from. Pages are to be used with the MobileApplication.Current.Transition function. You should not instantiate this class, inherit to use.

Object Model

Syntax

Visual Basic (Declaration)
<DesignerCategoryAttribute("Form")> <DesignTimeVisibleAttribute()> Public Class Page Inherits MobileForm Implements IPage, IPage2

C#
[DesignerCategoryAttribute("Form")] [DesignTimeVisibleAttribute()] public class Page : MobileForm, IPage, IPage2

Remarks

A page is essentially a form with additional implementations. In mobile application, a Task may consist of several pages, with each page containing certain information or getting user inputs. There are a few common properties on the page that you can customize, including the TitleBar, the SmallIcon, LeftSoftKey, RightSoftKey, and the WindowState. The default text for LeftSoftKey is set to "Back", and if tapped, will navigate user back to previous page automatically. One exception, though, is that the text will be changed to "Tasks" if previous page is Select Task Page. You can customize the text to your needs. If you want to take full advantage of your screen on a mobile device, set WindowsState to Maximized.

You are strongly recommended to build your page by inheriting Page class. This not only ensures a consistent look-n-feel accross various pages in the application, but also allows you to leverage MobileApplication.Transition method to navigate user from one IPage to the other with minimal development efforts. By using the Transition method provided by MobileApplication, you don't need to worry about how or when to show/hide old/new pages in a seamless way.

Application framework also provides a few customized UI components that you can use on your pages, such as DynamicPanel, ExtendedLabel, ExtendedListView, ExtendedTextBox, and so on.

On mobile device, users often want to use rocker or arrow keys to jump from one control to the other. Within application framework, the ControlFocusNavigator is provided for this purpose.

Besides the Page class that you can inherit, application framework also provides a few other pages that inherit from Page class with additional implementations. Based upon your use cases, you can use any of these pages by creating new instances. These pages are also heavily used inside of mobile application, including ViewAttributesPage and ListViewPage.

Inheritance Hierarchy

Requirements

Namespace: ESRI.ArcGIS.Mobile.Client

Platforms: Windows 98, Windows NT 4.0, Windows Millennium Edition, Windows 2000, Windows XP Home Edition, Windows XP Professional, Windows Server 2003 family, Windows Vista, Windows Server 2008 family

Assembly: ESRI.ArcGIS.Mobile.Client (in ESRI.ArcGIS.Mobile.Client.dll)

Object Model

Syntax

Remarks

Inheritance Hierarchy

Requirements

See Also

Reference

ESRI.ArcGIS.Mobile.Client
Page Class
Members See Also Send Feedback