http://bugs.meego.com/show_bug.cgi?id=4027
--- Comment #3 from ovek <[email protected]> 2010-07-27 02:18:26 PDT --- Well, the osso-abook API has methods of retrieving a full vcard of a contact, with the option of photo blob properly embedded. Perhaps it's better to use osso-abook than to hack up the Evolution backend, in case more is needed. What if you're syncing contacts with photos *to* the phone? Then, if using osso-abook, it might want to split out the photo to a separate file again, perhaps comparing with an existing file to avoid duplicates. But by bypassing osso-abook and using ebook directly, the old URI field will probably be overwritten with the actual photo data, and the database bloated with blobs and duplicate blobs, and the old detached photo files unused and wasting space. Handling something like that properly in the syncevolution backend would probably take platform-specific code anyway, I'm guessing. And in that case, the platform-specific backend may be cleaner anyway. -- Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching someone on the CC list of the bug. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
