Hi Patrick
I went through the API and the migration is very much doable. Sure
enough this will fix the live update of calendar issue. But the biggest
question I have is about the Timezone handling mentioned in
https://meego.gitorious.org/meego-middleware/kcal-eds/blobs/master/src/ekcal/ekcal-storage.h
"Custom time zones are those which do not match a system time zone.
Typically they come from importing an iCalendar 2.0 VCALENDAR. An app
must add all time zone definitions together with the incidences when
copying them between KCalCore::Calendar instances."
I am assuming that this is some thing Sync handles for the calendar app.
Right? Or is there more to the above quoted statement?
Thanks
Sirisha
On 05/13/2011 07:34 AM, Ohly, Patrick wrote:
Hello!
I got KCal-EDS to a point where I have a pretty good understanding of
how it'll work. The main API is defined in ekcal/ekcal-storage.h:
https://meego.gitorious.org/meego-middleware/kcal-eds/blobs/master/src/ekcal/ekcal-storage.h
Sirisha, can you check how well this fits the needs of the calendar app?
Is the documentation sufficient?
There are example and test programs in:
https://meego.gitorious.org/meego-middleware/kcal-eds/trees/master/test
The implementation is good enough to read and write simple events with
time zone information. Detached recurrences are not working yet. I have
code ready for it, but because of issues in the libecal API and
implementation, the result doesn't work yet. For the curious, here's
where I am discussing this:
http://mail.gnome.org/archives/evolution-hackers/2011-May/msg00001.html
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines
