Hello!

While studying the QtContacts [1] and KCalExtended [2] APIs, I spent
some time writing backends for them. Current state is that item
import/export and change tracking work.

QtContacts passes all Client::Source::qt_vcard30 tests except for
testImport. That's because its set of supported properties is different
from the Evolution test cases. For example, PHOTO does not seem to be
stored at the moment.

KCalExtended is still in rapid development right now. Just getting it to
compile and link requires fiddling with the KCalExtended source. It
fails some tests and is overall in a less stable state.

Both backends are not meant to be used for actual syncing and are not
supported - you have been warned ;-)

But I'd like to merge the code into the "master" branch anyway.
Yongsheng, can you do a normal code review of the "pohly" branch
(contains the some unrelated fixes for master) and a quick check of the
"qt" branch (based on "pohly", contains the new backends)?

[1] http://doc.qt.nokia.com/qtmobility-1.0/contacts.html
[2] http://maemo.gitorious.org/extendedkcal

-- 
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.


_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution

Reply via email to