[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-pim
Subject:    Re: [Kde-pim] Re: Generic XML conduit
From:       Adriaan de Groot <adridg () cs ! kun ! nl>
Date:       2001-06-28 11:03:25
[Download RAW message or body]

Since this thread started on the kpilot-list (?) I'll assume you're going
to want to talk to the Pilot itself. In that case, could I suggest that
you start with the code in kdenonbeta/kitchensync and *not* the current
KPilot setup? There are issues there, it's clunky and won't support USB
properly for some time, whereas the new stuff has that stuff already (but
no conduits, etc.).

On Thu, 28 Jun 2001, Cornelius Schumacher wrote:
> On Wednesday 27 June 2001 17:38, Johan Persson wrote:
> >
> > I have been thinking on writing a generic xml conduit. My first thought was
> > to write a conduit that synced my schedule (which I get in a xml format)
> > but then I thought that it would be much more fun to write a thingie that
> > could sync any xml document as long as there was another xml document
> > describing it according to rules put up.
> That's a good idea.

It is. But don't forget about the complexities of mapping this to the Palm
database formats -- or whatever device is there -- at the other end. There
are still precious few handhelds that actually use SyncML for anything.

> > This way is would be very easy to sync things that is available in the oh
> > so popular xml format.
> If you had some general syncing mechanism, you just would have to set up some 
> kind of description, how the xml data should be interpreted, what's the basic 
> unit of syncing, how to identify it, how to detect, if it has changed, etc. 
> This might not be possible for all xml documents, but at least, if you have 
> some control over the data in the document, it should be feasible.

Yes, and a very cool way of describing conduits in general. It might be
useful to have anyway, so that we have some way of describing
deconfliction algorithms, etc, needed by a particular conduit.


> > I have been looking around and I have not been able to find anyone else
> > working on something like this. I just thought I would do a last check
> > before starting designing.
> I proposed a general syncing library libKSync a while ago. A generic XML 
> syncer would be a great component for this. It looks like we really have to 
> start coding now... :-)

Yes, we do. I'm going on vacation, though, so I'm leaving the grunt work
to you guys :) Seriously, I want to polish up kitchensync enough so that
it does an actual Pilot backup, document it some, and leave it at that
till august.


-- 
To UNSUBSCRIBE from the KPilot mailing list, send a message
with subject "unsubscribe kpilot-list" and an empty body
to majordomo@slac.com.

Adriaan de Groot -- KPilot 4.0 (for KDE 2.x) maintainer
http://www.cs.kun.nl/~adridg/kpilot/


_______________________________________________
Kde-pim mailing list
Kde-pim@master.kde.org
http://master.kde.org/mailman/listinfo/kde-pim

[prev in list] [next in list] [prev in thread] [next in thread]