Hello! As discussed on meego-dev and internally, KCal-EDS and QtContacts-EDS are ready to be tested with apps. In order to get enough testing and to work out kinks we now need to get them into images. Here's a summary of what needs to happen. This is untested, let's see how it works out as we go...
Everyone, please check below for ARs. This migration is needed for MeeGo 1.2 and approval was granted to make the necessary changes, see: https://bugs.meego.com/show_bug.cgi?id=18690 - UX settings + SyncEvolution https://bugs.meego.com/show_bug.cgi?id=18678 - use EDS for contacts, calendar, email A bit related is removal of the timed dependencies: https://bugs.meego.com/show_bug.cgi?id=18560 - KCalCore + timed We already patched KCalCore; replacing mKCal with KCal-EDS will complete the removal of the calendar dependency on timed. EDS Contacts ============ * AR Chris Dumez: QtMobility needs to be updated to contain some critical bug fixes and change the search order of the default engine to "EDS, Tracker, memory" - this is for MeeGo 1.2 only, we need a better solution in Trunk (new upstream release?). * AR Chris Dumez: EDS needs to be updated, in Trunk and 1.2. We decided to package the latest source from the gnome-2-32 maintenance branch instead of carrying distro packages which were already reviewed and accepted upstream. * AR Connie and all app developers: avoid explicitly requesting the Tracker engine in QtContacts. Use the default constructor of QContactManager (without parameters) and you get the default engine on each image. Remove any runtime dependencies of your packages on qtcontacts-tracker. * AR Patrick: the SyncEvolution plugin for Buteo must also support Google Contacts (stop-gap measure until Buteo gets removed, see below). We are trying to get this done today. AR Praj: once all of this is in repos, switching to EDS Contacts in an image is done like this: 1. replace qtcontacts-tracker with qtcontacts-eds 2. replace syncevolution-qtcontacts with syncevolution-eds-contacts 3. remove buteo-service-google, replacement will be provided by syncevolution-buteo AR Praj: make these changes in the images using MeeGo UX. To go back to QtContacts-Tracker, revert steps 1 and 2 and clean your home directory (~/.sync, ~/.config/syncevolution) before syncing again. EDS Calendar ============ MeeGo UX Calendar App: * AR Patrick: KCal-EDS needs to be in Trunk and 1.2; must have a .pc file for apps * AR Chris: same EDS update as for contacts * AR Sirisha: rewrite the MeeGo UX calendar app to use KCal-EDS instead of mKCal; done, took her only a day or two. * AR Praj, everyone using the new calendar app: replace syncevolution-kcalextended with syncevolution-eds-calendar in the image There's no easy way to switch back and forth because accessing calendars cannot be hidden behind an abstract API, as in the QtContacts case. The on-going work of displaying calendar and clock alarms in the MeeGo UX is based on EDS, so we have to make this migration work. Goal is to to do this today. MeeGo UX Tasks: * AR Tej: go through the same steps as Sirisha. You can look at the calendar app source history to see what she changed. ekcal/ekcal-storage.h has some sample code and there are working examples here: https://meego.gitorious.org/meego-middleware/kcal-eds/trees/master/test MeeGo UX Clocks: * AR Patrick: add an API to KCal-EDS for creating a private calendar for clock events. * AR Emma: review API, use it in app. Migrating these two apps can be done independently of migrating the calendar app. With KCal-EDS it is easier to write apps which react dynamically to changes in the database. This is a long-standing gap in the current calendar app, let's address it quickly after the migration. SyncEvolution ============= * AR Gabriel: finish backend for MeeGo UX Settings which talks to syncevo-dbus-server. Initial version with support for SyncML was submitted for review. CalDAV requires further work. * AR Patrick: update SyncEvolution to provide the required Qt-based D-Bus client library and the CalDAV config templates. This doesn't have to be done together with the PIM migration. Contact syncing, at least with Google Contacts, will continue to work because SyncEvolution will be used inside the existing Buteo daemon + MeeGo UX Settings for it. -- Best Regards Patrick Ohly Senior Software Engineer Intel GmbH Open Source Technology Center Pützstr. 5 Phone: +49-228-2493652 53129 Bonn Germany _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
