The term UI controller refers to an object derived from either CAknAppUi or CAknViewAppUi, depending on your UI architecture. The UI controller is a required part of GUI-based applications.
Examples of services and responsibilities provided by the UI controller are as follows:
control stack for event handling
construction of views for applications
the top-level window owning control of the application
For more information on the UI controller, see:
The UI controller is part of the controller structure in the Model - View - Controller (MVC) design pattern used to design the architecture of many GUI-based mobile applications.
The CAknDocument -derived class of your application contains the first phase constructor of the UI controller.
The second-phase constructor is called by the application framework.
The UI controller is implemented in one of the following classes:
In a traditional architecture application architecture, the UI controller must be derived from CAknAppUi.
In Symbian view architecture, the UI controller must be derived from CAknViewAppUi.
In dialog architecture, the UI controller is typically derived from CAknAppUi.