On Fri, 2007-10-26 at 14:21 +0100, John Carr wrote:
> Lo all
>
> On Fri, 2007-10-26 at 14:05 +0100, Jonny Lamb wrote:
> > On Thu, 2007-10-18 at 23:40 +0100, Dr J A Gow wrote:
> > > For all who like to live on the fast lane at the cutting edge, I have
> > > committed an additional plugin module to sync-engine for OpenSync
> > > >=0.30. It's still experimental but I have had a good two-way sync with
> > > the file-sync OpenSync plugin (I believe the evo2 plugin in OpenSync SVN
> > > is broken and is being looked at by the OpenSync people, so this won't
> > > work yet).
> >
> > Despite the delay of my response, this is great news. Nice one, and nice
> > to see you around here again!
>
> The 0.3x plugin is great for me too - should be a doddle for me to get
> Conduit support going :-)
>
> > I spoke to Daniel Gollub from the OpenSync project, and he thought it
> > would be a good idea to have a 0.30-compatible SynCE-plugin in their
> > SVN. Thoughts? I could approach him on this topic and get you access if
> > you like? I'm not exactly sure about how dgollub was thinking this
> > should work..
>
> I am of the belief that the whole of SynCE stuff should be together.
> Theres already enough confusion about the version of synce that is in
> opensync svn.
>
> John
Regarding a SynCE plugin in OpenSync SVN - on the face of it it seems
like a good idea - but where do we draw the line between OpenSync and
SynCE?
What I mean is this: the plugin itself is just a single file containing
some Python. This is of no use on its own, but depends on sync-engine
for functionality. Would we put just the Python script in OpenSync SVN
and leave sync-engine in SynCE SVN? This would be one way forward but
would require a comprehensive README in with the Python script in
OpenSync SVN to avoid confusing anyone who needs WM syncing and comes at
it from the OpenSync site. We should certainly leave sync-engine in
SynCE SVN.
I wouldn't object to splitting it this way, but I tend to lean towards
agreeing with John on this one: that it would cause less confusion if we
keep SynCE stuff together. But if we could get a link on the OpenSync
site to our wiki and code, this may be a way to keep the OpenSync people
informed.
However:
Once the 0.3x plugin is working fully, one thing I am investigating in
the light of the changes in OpenSync's architecture is the way in which
sync-engine does its format conversions. For those who do not know,
OpenSync 0.3 spins off its format conversions into plugins. Currently I
am conducting a feasibility study in developing an OpenSync format
plugin with our AirSync<->XML format conversions in it, and subsequently
removing (or disabling) the format conversion code in sync-engine. This
would have a number of benefits: it would unburden sync-engine from
format conversions and allow it to speak native AirSync to the OpenSync
interface. Format conversions to OpenSync XML formats would then be
handled by the format plugin. This is more in keeping with the OpenSync
0.3x paradigm.
Such a format plugin should arguably be better residing in OpenSync SVN
as it would then expose the format to anything else out there that cares
to speak AirSync.
What do you all think about this approach?
Regarding the status of the OpenSync 0.30 plugin in SVN at the moment,
the actual sync process itself is flawless but the format conversions
are broken (i.e. the sync will happen but content will disappear from
synced items). OpenSync have changed the XML schemas considerably in
0.3x over 0.2x (and for the better, IMHO) . I am working on the format
conversions as we speak, and in my development tree I can now
synchronize event content cleanly with Evolution using OpenSync SVN.
I'll merge this new code with SVN as soon as I can find a way to do so
without breaking the existing 0.2x support. We'll have contact and task
support in the 0.3x plugin very shortly but I have some work to do to
implement the timezone conversions - OpenSync 0.3x has much better
timezone support than in the 0.2x schemas.
I'll keep you posted.
John.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
SynCE-Devel mailing list
SynCE-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/synce-devel
