On Mo, 2011-01-17 at 18:14 +0000, Sateesh Babu wrote: > On Fri, Jan 14, 2011 at 10:00 AM, Patrick Ohly > <[email protected]> wrote: > On Fr, 2011-01-14 at 04:57 +0000, Sateesh Kavuri wrote: > Now, in MeeGo core we don't have that option, so there's the conflict > between peer-specific modifications and general-purpose usage that I > had > in my email. > > How do you intend to resolve this conflict? By not adding > peer-specific > optimizations or with if/else decisions in hcontacts? > > For this reason, whatever the extra fields there are would be supported by > making use of generic vcard field support from QVersit parser and the generic > field storage mechanism from QContact.
There is no code in MeeGo yet which uses these facilities, is there? Is anyone currently working on adding such code? > > * We already discussed that the new implementation from QContacts > and > > QVersit parser should not result in data loss, since the data > should be > > stored transparently in the database, though the MeeGo contacts UI > might > > not make use of it. So, the idea is Buteo SyncML transparently > passes > > the vcard (through QContact object after being parsed by > QVersitParser) > > to QContacts and this inturn stores the object to the store > > "The new implementation" - sorry, but I lost track of what is already > implemented, in progress, or just a design idea. Can you be more > specific? > So, whatever fields there are from Google contacts that the MeeGo UI does > not support should still be stored to tracker and I believe the Contacts > engine > has made the necessary changes for it. So we (you can provide a patch if you > have one) could check the new implementation from QContacts and see if > it works (http://bugs.meego.com/show_bug.cgi?id=4897#c14) We looked into it and found that it least one corner case, the ORG property, cannot be handled using that API. Now this might not be important, so let's assume that the QtContacts API is sufficient. How should hcontacts be modified to make use of it? The information about which details are to be modified needs to come from somewhere. This goes back to my original question whether an "if(is_google)" check in hcontacts would be okay, and how to check for that. > About the XML profile patches, when can this be integrated? The bug in > the profile currently blocks all testing with Google Contacts in > MeeGo. > > We will take this up. The google contacts sync without the credentials in the > other XML seems to be more of a bug. Thanks. The bug is the missing client profile reference, the credentials is merely cosmetic. -- 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
