> Calendar > ======== > > QtMobility Calendar: > unique ID under debate, see > http://developer.qt.nokia.com/forums/viewthread/363/ > > mkcal: > combination of UID + RECURRENCE-ID (optional) + calendar file, > change notification only via coarse "calendar has changed" in > SqLiteStorage, > time zone changes from timed > > Tracker: > NEPOMUK Calendar Ontology (NCAL), > pushed by mkcal Sqlite storage, > only ncal:uid seems to be set, RECURRENCE-ID is mangled into item ID, > detailed changes via SopranoLive::BackEnds::Tracker::ClassUpdateSignaler? > > See > http://meego.gitorious.com/meego-middleware/mkcal/blobs/master/src/tracker > modify.cpp > > Question: serializing a RECURRENCE-ID into a single string is hard > because it is a DATE-TIME value + TZID (iCalendar 2.0) resp. a KDateTime > (mkcal). What is the recommended way of serializing it?
The id in tracker has to be unique, so the recurrenceId is used to make it unique. And of course no TZ is included there, so the "easiest" is using UTC. > > It seems that RECURRENCE-ID is stored in Tracker, but only after > conversion to UTC and without milliseconds: > // The format supported by tracker is not really ISO8601, as it > // doesn't support milliseconds. Therefore we eliminate those here. > QString kdatetime2String( KDateTime dt, bool toUtc=true ) > > Question: ignoring the problem with milliseconds here (doesn't matter > for iCalendar 2.0), can mkcal find the original incidence when it has a > RECURRENCE-ID using a time zone and the query uses UTC? > mkcal doesn't need to open tracker, at least not at the moment. mkcal is just pushing contect to it. _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
