Well, I have implemented some basic libicalsupport in a php extension which can be found at http://www.braindump.dk/dk/wiki/index?wikipage=ICalendarExtension

It's in no way complete, but it has the functions I need...

assigning to myself.

Is anyone currently working on this?  I have an implementation that is about 25% complete at the moment based on PHP 4.3.2 and libical 0.23.  The page at braindump.dk appears to have been taken offline.

The company hosting my site went down, so my extension can be found at
http://www.itcampus.dk/studenternet/ical-0.2.tar.gz
if anybody is interested.

In the time since I posted I've written up a nearly-complete implementation of the libical bindings, but I took a different approach: I treated each type as a class, with the ultimate goal of writing PHP code like so:

  $x = ical_new_vcalendar();
  $y = ical_new_vevent();
  $y->add_property(...);
  $y->add_property(...);
  $x->add_component($y);
  print $x->ical_string();

Comments?  Personally, I would prefer that we had a coordinated effort on this rather than developing two incompatible versions of the libical bindings; feel free to contact me directly at the email address shown above.

Example implementation including parser and calendar manipulation functionality is located at

http://www.a-s-i.com/~glamm/ical/

Despite the "alpha" tag, most of it works.

Just an update -

I don't plan to make the ical extension I've listed anything more than a beta/patch to PHP 4.  Instead, the ical extension will be targeted to PHP 5 using the improvements in the Zend engine (__construct()/__destruct(), __toString(), static methods, class constants, etc.).  The library that the ical extension is based on fits the improvements in ZE2 better than the engine in PHP 4.

I expect it will be a few months before it's complete, however.

Hello. Any update on this bug? Bob, where did you move your parser work? Do you still have it?

Since there was a lot of work done it seems on such function, it should be proposed to be moved into PECL if this is still desired, but chances that we will implement a new extension and directly submit to the core is really rare nowadays so I'm closing this.