On Fr, 2011-06-10 at 16:02 +0100, Dumez, Christophe wrote: > I noticed recently that QtVersit tries to map QContactOnlineAccount to > their X-* vCard equivalents (e.g. X-SIP). This is nice for > interoperability but carries an important limitation: only the > AccountURI field is saved. The other fields (Protocol, capabilities, > provider) are simply dropped. > > The following bug report against qtcontacts-tracker from Kaitlin seems > to be indicate that this may be too restricting for app developers: > https://bugs.meego.com/show_bug.cgi?id=13454 > > The patch attached for qtcontacts-eds overrides QtVersit's mapping and > saves to a X-EDS-QTCONTACTS extension instead so that all the > QContactOnlineAccount fields get exported / imported from the vCards. > > I haven't committed the patch to our GIT repository yet because I'm > not sure which behavior is expected. We need to make a choice between > interoperability and completeness.
We should favor completeness. > I would personally prefer to use the patch since reliable contact > saving is the main target and interoperability through vCard export is > only secondary IMHO. Agreed. The QVersit provided by QContacts-EDS defines the "MeeGo vcard flavor." Translation into other flavors is part of synchronization and depends on knowledge about the peer. Simply exporting/importing a vCard doesn't have that context and therefore should use the local context (= MeeGo vcard flavor). -- 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
