diff -r 51a74ef9ed63 -r ae94777fff8f Symbian3/SDK/Source/GUID-BDDDF68F-F7C3-43AF-8B6C-C77C701FD2A9.dita --- a/Symbian3/SDK/Source/GUID-BDDDF68F-F7C3-43AF-8B6C-C77C701FD2A9.dita Wed Mar 31 11:11:55 2010 +0100 +++ b/Symbian3/SDK/Source/GUID-BDDDF68F-F7C3-43AF-8B6C-C77C701FD2A9.dita Fri Jun 11 12:39:03 2010 +0100 @@ -1,72 +1,72 @@ - - - - - -Framework -requirements for GUI applications -

Applications developed for the Symbian platform can use a number of -different architecture solutions to meet their requirements. One example of -a common approach includes the Model - View - Controller (MVC) pattern used -in GUI-based applications. In this approach, the application is split into -three separate logical parts. Each part contains a different aspect of the -entire application, and has a specific role.

-Logical dependencies in the MVC pattern -

In this approach, the model:

- -

the view :

- -

the controller :

- -

The pattern is implemented with the following classes.

-Relationship between the classes that make up a typical Symbian application -

The CAknApplication-derived class:

- -

The CAknDocument-derived class:

- + + + + + +Framework +requirements for GUI applications +

Applications developed for the Symbian platform can use a number of +different architecture solutions to meet their requirements. One example of +a common approach includes the Model - View - Controller (MVC) pattern used +in GUI-based applications. In this approach, the application is split into +three separate logical parts. Each part contains a different aspect of the +entire application, and has a specific role.

+Logical dependencies in the MVC pattern +

In this approach, the model:

+
    +
  • contains and manipulates the data in the application

    +
  • +
  • is owned by the controller

  • +
  • is typically implemented in its own class or classes

    +
  • +
+

the view :

+
    +
  • displays the application state known by the model

    +
  • +
  • receives user input

  • +
  • notifies the controller of relevant events

  • +
  • is implemented either with a CCoeControl derived +class or a CAknView derived class.

    For more +information on these options, see Traditional +Symbian UI application architecture and View +architecture.

  • +
+

the controller :

+
    +
  • handles application-wide events

  • +
  • commands the model, typically based on user input

    +
  • +
  • selects the view to be displayed

  • +
  • is implemented either with a CAknAppUi-derived +class or a CAknViewAppUi derived class.

    For +more information on these options, see Traditional +Symbian UI application architecture and View +architecture.

  • +
  • requires the implementation of CAknApplication and CAknDocument derived +classes.

  • +
+

The pattern is implemented with the following classes.

+Relationship between the classes that make up a typical Symbian application +

The CAknApplication-derived class:

+
    +
  • provides the application object expected by the application +framework when the application is launched.

  • +
  • defines the application properties.

  • +
  • creates the CAknDocument derived class +if it does not exist yet.

  • +
  • if an instance of the application is already running, switches +to that instance and exits.

  • +
+

The CAknDocument-derived class:

+
    +
  • creates the controller class

  • +
  • is the base class for application documents

  • +
\ No newline at end of file