On Fr, 2010-09-17 at 10:49 +0100, [email protected] wrote: > >Contacts > >======== > > > [snip] > > > >QVersit: > >incomplete (?) subset of QContact > > The versit module tries to provide complete (and round-trip-stable) > conversion between a QContact and a vCard. However, different > backends can have their own definitions/schema for data, and so the > versit modules provides hooks to allow synchronization agents to do > their own mapping for specified data types / fields.
Let me make the question more specific: on MeeGo, we only have one supported backend. QtVersit on MeeGo should fully support data in that backend by default. How can we make that work? The alternative is that every app importing/exporting data on MeeGo needs to come up with its own mapping. This is not just duplicating code, it'll also be fraught with interoperability issues (different mappings => data loss). To give just one example, Buteo's hcontact storage plugin currently contains no code to add any mappings beyond those supported by QtVersit out-of-the-box. Sateesh, how would you like to see this handled: add code to hcontact or create a default MeeGo QtVersit extension? Perhaps Buteo is a bad example because it needs different mappings to be interoperable with different existing peers, but the general idea still holds. -- 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
