Thursday, December 07, 2006

OpenSync progress redux

More work on the Opie plugin for OpenSync. After testing synchronisation with KDE PIM it seems there are still a lot of bugs. I fixed quite a few obvious ones, but a major problem that still remains is UID mapping. If you create an entry on the non-Opie side it doesn't have a unique ID that Opie understands, so when that entry is synced across and subsequently modified by Opie it gets assigned a new one. At the next sync it appears to OpenSync as a new entry and so you get a duplicate item. This pretty much makes the plugin useless at the moment, but I think I know how to fix it.

It's nice to finally have a few users testing the plugin too - it gives me some motivation to keep working on it :)

3 comments:

zecke said...

Hey Paul, with the old KitchenSync and on OSX/iSync we use the obvious solution and save the mapping from system UID to the one we assign to Opie. IIRC OpenSync already provides a system to save those.

Keep on rocking!

Anonymous said...

Hi Paul,

tested you work in OpenSync 0.20 and it worked rather well for the file-plugin, apart from the fact that the timestamps are in the local TZ (MET), not GMT. When using the file repository to subsequently sync with my mobile all entries are one hour off...

Blue Lightning said...

bofh wrote:
> the timestamps are in the local TZ
> (MET), not GMT. When using the file
> repository to subsequently sync with
> my mobile all entries are one hour
> off...

This was a problem with the OpenSync core that has now been fixed in svn. You can grab the latest source from svn, or wait for the next release.

BTW, I'm mainly working on the Opie plugin for OpenSync, others must get the credit for OpenSync itself :)