On Mo, 2011-05-16 at 08:03 +0100, Muppavarapu, Sirisha wrote: > I went through the API and the migration is very much doable.
Are there any additional API calls that you (or anyone else) would like to see added? For example, loading only events relevant for a certain time range? EDS does that fairly efficiently. For example, it is not necessary to load all recurring events. I know that the calendar app does not currently do that with mKCal, which is why it isn't in the API of KCal-EDS already. I don't want to make the migration any harder than necessary, but it may be worthwhile. > 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? Depends on whether your app ever works with more than one calendar. > Or is there more to the above quoted statement? If your or some other app imports an .ics file, it will have to do the same thing: * parse .ics file into memory calendar * move time zone definitions * move events The last two steps are tricky. I asked the mKCal and KCalCore developers whether there is utility code which gets all the corner cases right, but there is none. See: https://bugs.meego.com/show_bug.cgi?id=8604 http://lists.kde.org/?l=kde-pim&m=130440594019927&w=2 My intention is to add this, like I did a while ago for libecal, and either offer it as part of KCal-EDS or KCalCore (depends a bit on how generic it'll be). In the meantime, don't worry too much and just copy time zone definitions together with the events, without any additional checks. QA and most users will never find out that these corner cases are not handled >:-> Seriously, this needs to be fixed eventually. It's just that there are bigger fish to fry first. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
