View Architecture Overview

Allows applications to make and receive requests to show a particular view of their data. Applications can also pass small amounts of data in such requests. The view architecture allows applications to have a fine level of integration between their user interfaces. This particularly allows the user to navigate through the UI on the basis of the task they are working on, rather than perceiving separate applications.

Views are UI controls, derived from the abstract view interface, that display application data. They are typically owned by the application's main user interface class (the App UI), which is derived from the framework provided by the Uikon Core API (CEikAppUi, and its base class from the UI Control Framework, CCoeAppUi).

The interprocess communication required to make and receive requests to display particular views is handled by a dedicated server. The client/server interface is not used directly by applications, but through wrapper functions in the App UI framework (CCoeAppUi).

The API has two key concepts: abstract view interface, and view ID.

The abstract view interface is implemented by application views to receive activation and deactivation requests from the view server. The activation method allows a message (a Direct Navigational Link, or DNL), encapsulated in a descriptor, to be passed to the view (e.g. the name of a file that should be displayed in the view). Note that the view architecture does not impose any other policy on what type of object implements the view interface.

The abstract view interface is provided by MCoeView.

The view ID identifies a view uniquely. It includes the application UID and another UID for the particular view.

The view ID is provided by TVwsViewId.

UI Control Framework Overview

Uikon Core Overview