On Sun, 2009-09-06 at 14:18 +0100, William Uther wrote:
I've just recently bought an HTC Hero phone and was looking to sync
it with my Mac. It looks like SyncEvolution might be a piece of that
puzzle, so I was going to play with updating the mac plugin to version
0.9. I'm not sure I want to take on a long term maintenance role
I'm new to this. I'm just downloading the code now. Is there
anything you want to tell me before I start?
Dig in! ;-) Seriously, this is excellent news, no matter what the
outcome will be.
The most important open question before you start is how the data
handling will work with direct access to the Synthesis field list. If
you haven't seen it, here's an introduction to the concepts:
In particular, I came across this in the list archives:
> For Mac OS X there isn't much choice: the code depends on the
> Funambol "VOCL" vCard encoder/decoder, which is no longer available.
> Short of adding it again (either the old GPL-licensed copy or the
> current AGPL one) there's nothing that can be done in 0.9. It should
> be rewritten to access the Synthesis field list.
Any estimates on how much work that would be?
Once you understand the concepts, it might be anywhere between a few
hours of coding and some days. The biggest "problem" is that we don't
have an example of a sync source which demonstrates how to access the
Synthesis field list. The only example is in
SyncSource.cpp:SyncSourceLogging on the master branch.
Congwu, you wanted to look into adapting the SQLite example sync source.
Any idea when this might be done? I'm sure it would help William; on the
other hand, we also need some of your time for the direct-sync feature
(in-process OBEX client), that's also important.
Finally, there seemed to be talk of making syncevolution run as a
server (using Synthesis?). Is this currently planned? If so, is it
far future, near future...?
It's definitely near future. I've posted a schedule last week here on
the list, aiming for a release end of October. If it works out as
planned and how much really works remains to be seen - it's certainly an
ambitious timing. No risk, no fun...
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.