According to Tom Foottit <[EMAIL PROTECTED]>: > We use libversit in 2 places. It is in the Evolution plugin, but I don't > think it is required (at least not any more). The Evolution plugin > doesn't call it directly - it actually makes a few calls to libical > (includes ical.h). > > The libversit in multisync/src is currently only being used by the Opie > plugin. I have modified it so fix some bugs and include support for > recurring events, alarms, etc. When I started the Opie plugin this past > winter I did not know anything about parsing iCal/vCal/vCard and I > turned up libversit after some searching. I modified it to do what I > needed.
In fact, what we'd really need is totally abstract the data model. So conduit send and receive MultisyncEvents, MultisyncTodos, MultisyncCards. Then they get converted to whatever is appropriate. For example, Evo would get iCalendar and vCard (or perhaps its own data type), and a Pilot conduit would transform these to .pdb or whatever. In short datafile format should be abstracted and only meant for persistent storage (file output), or to communicate with other devices that requires it. libical has one advantage is that it offers a really versatile data model for Events and Todos, and we might find something similar for vCards (and if we don't, try to map one that match the vCard model, versatile to be extensible). > I agree that we should be using libical for calendaring/todos and > libversit for vCards. The libical API looks much nicer, and will > probably provide more features. There are a few problems: libversit seems to be quit aged in regards to RFC for vCards, so may I suggest to look for a replacement. > 1. Rewriting opie_vtype.c to use libical will take some work and a lot > of retesting to make sure I don't break anything. Sure. > 2. As Mika Raento mentioned, there is a libical-evolution in use by the > Evo plugin. We either have to use it or end up with symbol conflicts. Can't we just weak link with Evo ? > 3. libical isn't shipped by all distributions. It doesn't seem to be in > RedHat, although it looks like it is in Debian (unstable anyway). It is in Debian/sid. Anyway I don't think it is a real problem. Packaging should not be our business, but making packagers life easier should be. Hub -- AbiWord maintainer - Lille, France http://www.figuiere.net/hub/ GPG fingerprint: 6C44 DB3E 0BF3 EAF5 B433 239A 5FEE 05E6 A56E 15A3 ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Multisync-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/multisync-devel
