View +Server Tutorial

The UI Control Framework (CONE) provides CCoeAppUi that +provides an interface to the View Server, which enables seamless switching +between different views across various applications.

Introduction

The UI framework built on Cone/uikon +can make a choice to use the View Server.

The view architecture allows +applications to make and receive requests to show a particular view of their +data. It allows applications to have 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. +For example, an application provides a view of a given Contact, any other +application may display a contact using that view.

Views are UI controls +that are derived from the MCoeView abstract view interface +and display application data. Typically views are top-level window-owning +controls. Each view is given a unique identifier of type TVwsViewId. TVwsViewId is +a combination of the UID of the application and the UID of the view within +the application. An application participating in the view switching must complete +the steps given in the procedure section.

Procedure

Create +an instance of CCoeAppUi
Implement +the observer functions to get notification on events, if required.
Derive +a class from the MCoeView class.
Add +the view to the control stack to receive key events.
Register +the view with the View Server.
Perform one or more +of the following tasks:
1. Activate +a view through the client session.
  
  If the view which has to +be activated is not registered with the server when an activation request +arrives, the view server starts the application associated with that view.
2. Set +a view as a default view.
3. Deregister +a view, if required.