On Fri, 2005-01-07 at 09:26 +1100, Stewart Heitmann wrote:
> >
> > Out of interest, I a wondering if you are actively working on the
> > sync_vtype_convert stuff at the moment.
> > Your original post suggested that you were, and I am wondering what
> > direction you are heading and on which branch you are working.
Ah, no. I realized that for the syncml stuff to work, there would be a
need to:
1 maintain the devinf
2 really parse the devinf
3 do right version conversions
4 filter/transform on supported fields only
1 and 3 are alright, 2 is not too bad but 4's the clinch. As it relates
to syncml, I realized I'd have to go and really read the specs to
understand how we are supposed to handle the different capabilities of
the different devices, which I haven't got the time for right now at
least.
To me atleast it's also an open question whether the Syncml devinf is
powerful enough to actually encapsulate the real device differences or
whether we'll have to add device-specific conversion code to the plugin
in the end.
The idea of using an XML structure for the data would allow us to use
XSLT transforms for the device-specific stuff as needed (on a semantic
level - if it needs certain manipulation of the actual
VCARD/VEVENT/whatever syntax, then that's of course not possible). That
might be of a problem than a solution though.
Regards,
Mika
--
Mika Raento mailto:[EMAIL PROTECTED] http://www.iki.fi/mikie/
"You can't *ADD* things and come out with *LESS* than you started with!"
"I can do that! It's a free country! I've got my rights!"
-from Calvin & Hobbes by Watterson
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Multisync-devel mailing list
Multisync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/multisync-devel
