Calendar application and backend for Ubuntu Touch

Registered by Bill Filler on 2013-05-09

Calendar application and backend for Ubuntu Touch

Blueprint information

Status:
Not started
Approver:
None
Priority:
High
Drafter:
Bill Filler
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
Accepted for saucy
Implementation:
Unknown
Milestone target:
milestone icon ubuntu-13.10

Related branches

Sprints

Whiteboard

== Client API ==
Calendaring clients for Ubuntu Touch will use QtMobility api's. Specificially, applications should use QOrganizer and related classes as found here:
http://doc.qt.digia.com/qtmobility/organizer.html.

This is consistent with the approach being used for Contacts, which uses QContacts from QtMobility as specified here: https://wiki.ubuntu.com/Touch/Specs/ContactsService.

Clients should instatiate the default manager (QOrganizerManager) for the Ubuntu Touch platform to access the default backend for the platform.

Example client code can be found here:
http://qt.gitorious.org/qt/qtpim/trees/master/examples/organizer/qmlorganizerlistview

== Backend ==
EDS will be used as the backend for Calendaring, but this will be abstracted by the QOrgranzer classes which provide client access. Clients should not use EDS api's directly, but rather the QOrganizer classes.

On Ubuntu Touch a QOrganizerManagerEngine plugin will be written that interfaces with EDS, and this will be set as the default provider for the platform. Until this plugin is written, there are two engines that can be used for development: an in-memory engine and a JSON-document file engine.

(?)

Work Items

Work items for ubuntu-14.04:
[renatofilho] improve unit test: DONE

Work items for ubuntu-13.07:
[renatofilho] write QOrganzierManagerEngine plugin for EDS: DONE

Work items:
[renatofilho] provide qt-jasondb package to use for temporary storage: DONE

Dependency tree

* Blueprints in grey have been implemented.