|
|
| Line 1: |
Line 1: |
| == Contour Tasks == | | == Contour Tasks == |
|
| |
| === Akonadi Qt-Mobility integration ===
| |
| For optimal Meego-compatibility a bridge between Akonadi and Qt-Mobility is required. This essentially means three sub-tasks:
| |
|
| |
| * The Contact Manager Engine provides an implementation of [http://doc.qt.nokia.com/qtmobility-1.1/qcontactmanagerengine.html QContactManagerEngine] as a backend for [http://doc.qt.nokia.com/qtmobility-1.1/contacts.html The QtContacts framework].
| |
| * The Organizer Manager Engine provides an implementation of [http://doc.qt.nokia.com/qtmobility-1.1/qorganizermanagerengine.html QOrganizerManagerEngine] as a backend for [http://doc.qt.nokia.com/qtmobility-1.1/organizer.html The QtOrganizer framework].
| |
| * The Messaging Integration in Qt-Mobility is slighly more complicated than contact or organizer item storage since the [http://labs.qt.nokia.com/2009/09/21/introducing-qmf-an-advanced-mobile-messaging-framework/ QMF] framework is not pluggable. There is no way for storing messages in Akonadi without patching Qt-Mobility itself. It is unclear whether this is worth the effort at all.
| |
