---- Reported by email@example.com 2010-03-29 22:13:38 +0000 ----
This is from http://bugzilla.moblin.org/show_bug.cgi?id=6433
Description From jku 2009-09-24 23:52:39 PST
People are asking us to support Google calendar sync. Strictly speaking that's
not possible since Google doesn't do SyncML for calendars, but they do have
caldav support... Caldav is not really synchronization, but it might easily be
good enough for many people.
EDS has a caldav backend that apparently works, so the groundwork's been done
already. We need to:
* figure out where the caldav data is consumed: in Dates itself or should
SyncEvolution have some evil caldav-via-eds-backend (I'm not sure this is
possible, just thinking aloud)
* add the setup UI somewhere. In the future I'd say it should be wherever the
rest of "web service setup" (which will include syncevolution setup) is.
------- Comment #1 From jochenh 2009-09-25 06:38:12 PST (-) [reply] -------
OpenSync can sync with google calendar. There is a special Plugin for that.
Lighting and Evolution have Google Calendar support. There is a google calendar
provider for lighting: https://wiki.mozilla.org/Calendar:GDATA_Provider
-------- Comment #4 From pohly 2010-03-29 06:21:01 PST (-) [reply] -------
It's certainly a worthwhile feature request which deserves some attention. Let
me do some investigations and report back.
---- Additional Comments From firstname.lastname@example.org 2010-03-29 22:15:22 +0000 ----
I put this issue in syncevolution upstream (from original other component). If any component of Meego should do any supporting, I will move to it then. Thanks!
---- Additional Comments From email@example.com 2010-04-09 07:53:21 +0000 ----
(In reply to comment #0)
> EDS has a caldav backend that apparently works, so the groundwork's been done
I looked into that and found that it doesn't work well enough for us. For example, e_cal_create_object() doesn't return the new ID, which is crucial for us.
My conclusion is:
1. We need a better solution for backend A<->backend B syncs (I sometimes call that "local sync").
2. We should better write a CalDAV backend instead of relying on EDS. Not only will that avoid the issues, such a backend would also be useful for users not interested in running EDS and perform better. I'm assuming here that CalDAV has functionality that would helps us (like efficient listing of all items) which we can't use when going through EDS because it doesn't have corresponding APIs.
--- Bug imported by firstname.lastname@example.org 2012-08-19 20:56 UTC ---
This bug was previously known as _bug_ 319 at https://bugs.meego.com/show_bug.cgi?id=319
Unknown platform unknown. Setting to default platform "".
Unknown operating system unknown. Setting to default OS "".
Solved already a while ago... see local sync and CalDAV/CardDAV backend.