Avkon controls

Building an Avkon-based application UI is a primary choice for third-party add-on applications that do not need specific visuals. Such an approach guarantees compatibility across different S60 Developer Platform editions, but, in turn, puts some limitations on the application UI layout imposed by Avkon. Avkon provides a wide choice of well-designed and versatile components, but not all of these are easily modifiable. Here we will look at each group and see what elements can be modified in the controls. A full description of UI elements appears in the S60 UI Style Guide.

All of the Avkon controls considered below, except dialogs, are non-window-owning controls, which means that they cannot exist on the screen without being inside a container window.

In the examples below, a dialog is used to hold the components; this is typically defined within a resource file . The application developer generally uses a dialog or creates a blank view /container control (derived from CCoeControl), which will hold the Avkon controls.