[jp] Interoperability

Dan Stromberg strombrg at dcs.nac.uci.edu
Tue Jan 18 18:30:23 EST 2005


On Tue, 2005-01-18 at 15:05 -0400, Adam Richard wrote:
> Quoting Jason Day <jasonday at worldnet.att.net>:
> 
> > A couple years ago, I started a jpilot-icalendar project to do exactly
> > this.  I started with an icalendar import program, which imports .ics
> > files into J-Pilot's calendar.  It works well enough for me, but it
> > still needs some work, and I lost the motivation to make a full-fledged
> > icalendar sync conduit.  Especially when I realized how difficult it
> > would be :)  If anyone is interested, the importer is available here:
> > http://jp-icalendar.sourceforge.net/
> 
> What made it difficult?  The J-Pilot conduit API (or whatever you call it) or
> reading/writing the iCalendar file format?

I'm a tangentially related subject, while I'm a devoted fan of python, I
noticed that there is apparently a ruby interface to ocal/corporate
time, which use the IETF-defined ical format (not the ancient *ix app)
internally.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://lists.jpilot.org/pipermail/jpilot_lists.jpilot.org/attachments/20050118/6d401423/attachment-0001.asc>


More information about the Jpilot mailing list