Docstoc

architecture council charter _ working practices

Document Sample
architecture council charter _ working practices Powered By Docstoc
					Qt Direct UI

Technical Solution Description
Draft v0.1


Contents
1        Contribution ................................................................................................................... 1
2        Architecture Overview.................................................................................................... 2
    2.1         Software architecture diagram ............................................................................... 2
    2.2         Additional information ............................................................................................ 3
3        Configurability (device software only) ............................................................................ 4
4        Interface management ................................................................................................... 4
    4.1         New or modified public APIs .................................................................................. 4
    4.2         New or modified platform APIs ............................................................................... 4
5        Usage of Application Framework ................................................................................... 4




1 Contribution
Development proposal ID
TBD


Feature description


Content
           A renewed application touch UI layer built on top of Orbit and Qt supporting Touch UI
            and Touch/Keyboard hybrid devices. In addition, some application may also choose
            to rewrite application engine level code on top of Qt.
           Qt based application interworking APIs, which are required for UI level interworking
            between the applications.
           Qt based plug-in APIs extending Qt plug-in mechanisms with Symbian ECOM
            features.
           Number of different Qt wrappers developed on top of existing Symbian engines in
            order to keep Qt code and Symbian code separated in a controlled manner.


Impact
           This contibution is replacing Avkon based Application layer with Qt based
            applications.



                                                                     1
          Application set is simplified, thus the number of applications will be reduced.
          Avkon based applications will not be further maintained. Avkon is maintained only on
           those parts, which is needed for supporting Qt port.
          Extension applications on top of Direct UI release can not be expected to be Avkon
           based. Extension applications can be implemented on top of Qt, existing Qt UI
           widgets and Orbit UI widgets.
          New Qt applications will not support same Application interworking APIs as current
           Avkon based applications do.
Applications and UI framework must be re-implemented in order to match with the
competition and for utilising graphics HW capabilities better.



2 Architecture Overview


2.1       Software architecture diagram




Applications
          Complete set of applications replacing the existing applications. The exact list of
           applications is not yet final, but the number of application will be reduced.




                                                   2
Qt AIW “Application interworking” APIs
          Symbian Application server mechanism wrapped on Qt
          Symbian ECOM server wrapped on Qt.
          Dynamic Orbit widget loading.


Qt wrappers on top of Symbian APIs
          Publish&Subscribe
          Wrappers on existing configuration mechanisms
              o   Feature manager API, Central repository API.
          Etc.


Applications are separate processes as in current architecture. Some application
architectural and design differences expected with renewed UI navigational model and
because of limited HW graphics memory. Details are not yet known at the moment.


2.2       Additional information


Duplication of platform functionality
It is duplicating existing application UI layer.


Start-up and shutdown
No significant architectural changes expected.


Power management
No specific issues expected.


ROM Memory Management
Information is not yet available.


RAM Memory Management
Information is not yet available. Some level on Autosave/Exit functionality is expected,
because of limited HW graphics memory.


Platform security
No specific issues seen.


Performance
Main issues are related to Qt port and Orbit. No specific issues in application level seen.


                                                   3
Dependencies on tools
Qmake changes needed in order to generate Symbian Application server and Ecom glue -
codes.




3 Configurability (device software only)
Existing configuration tools are used.
Applications will support touch and touch/keyboard hybrid devices.



4 Interface management
4.1   New or modified public APIs
AIW APIs implemented by Avkon Applications are by default deprecated, although in any
case, they are under normal API management control. Other APIs implemented by
application domains are not by default deprecated and under normal API management
control.


4.2   New or modified platform APIs
AIW APIs implemented by Avkon Applications are by default deprecated, although in any
case, they are under normal API management control. Other APIs implemented by
application domains are not by default deprecated and under normal API management
control.


5 Usage of Application Framework
Contribution uses Orbit UI Framework.




                                             4

				
DOCUMENT INFO
Shared By:
Categories:
Stats:
views:24
posted:2/2/2010
language:English
pages:4