The following image illustrates the components of the view architecture approach.
Symbian platform applications that follow the view architecture require:
The view architecture only allows one view to be active in each application. If a new view is switched to within an application, the current view is immediately deactivated, so this architectural approach is not appropriate in the following cases:
Applications with any view that cannot cleanly handle unexpected activation of another view in that application.
Applications that provide views that can be nested over other applications, except where embedding is used.
Applications that provide controls that can be used inside other applications (for example, using a Web control inside an e-mail viewer to show an e‑mail with HTML content).
Typical responsibilities in this architecture are:
CAknViewAppUi -derived class acts as a UI controller :
It creates one or more CAknView -derived view controllers.
It handles events that are not handled by the view controllers.
To switch between views, it activates and deactivates views.
It handles menu commands passed to it by the view controllers.
CCoeControl -derived view:
Shows application data and state on the screen.
Copyright ©2010 Nokia Corporation and/or its subsidiary(-ies).
All rights reserved. Unless otherwise stated, these materials are provided under the terms of the Eclipse Public License v1.0.