On Fr, 2010-09-17 at 10:49 +0100, [email protected] wrote: > >Calendar > >======== > > > >QtMobility Calendar: > >unique ID under debate, see > >http://developer.qt.nokia.com/forums/viewthread/363/ > > It's been decided to allow the engine to provide their own custom id > type, in the Qt Mobility Organizer API. > The problem arose from the way in which items could be uniquely > referenced by clients; on some platforms this requires extra > information than just the event-id (for example, the filename of the > calendar file in which it is stored, the notebook name, the datastore > name, etc etc).
Please remember to include a to/fromString() method as part of the custom id type. This will be necessary to store such an ID on disk or pass it between programs (D-Bus, command line, ...) How to implement that however may be an unsolved problem, see the discussion around serializing mkcal's KDateTime for the RECURRENCE-ID part. -- 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
