Mailing List Archive

Hi Ewout,

El 17/10/11 14:45, Ewout de Langen escribió:
> Is there a good and solid Object Oriented php wrapper to communicate
> with a Davical Server without having to handle/dive into the ICal
> format.

This is not exactly what you're looking for, but you could try AgenDAV
( http://agendav.org/ ), which is a CalDAV web client I'm developing and
it's fully functional. It still lacks some features, but I hope it to be
more powerful as its development goes on.

On its backend it's based on iCalcreator
(http://www.kigkonsult.se/iCalcreator/) for iCalendar parsing and
handling, and davical-client-v2 from DAViCal for CalDAV protocol operations.

Regards.

--
Jorge López Pérez
http://adobo.org
Jabber: jorgelp@jabberes.org
_______________________________________________
DAViCal-dev mailing list
DAViCal-dev@lists.davical.org
http://lists.davical.org/listinfo/davical-dev

Hello Jorge,

2011/10/18 Jorge López Pérez <jorge@adobo.org>:
>> Is there a good and solid Object Oriented php wrapper to communicate
>> with a Davical Server without having to handle/dive into the ICal
>> format.
>
>  This is not exactly what you're looking for, but you could try AgenDAV (
> http://agendav.org/ ), which is a CalDAV web client I'm developing and it's
> fully functional. It still lacks some features, but I hope it to be more
> powerful as its development goes on.
>
>  On its backend it's based on iCalcreator
> (http://www.kigkonsult.se/iCalcreator/) for iCalendar parsing and handling,
> and davical-client-v2 from DAViCal for CalDAV protocol operations.

Thank you, AgenDAV and iCalcreator look very interesting!

We noticed that a recurring event is not communicated to the frontend
as 1 event, but as multiple separate single events. Why did you take
this design decision?

Regards,
Ewout
_______________________________________________
DAViCal-dev mailing list
DAViCal-dev@lists.davical.org
http://lists.davical.org/listinfo/davical-dev

Hi Ewout,

El 19/10/11 10:28, Ewout de Langen escribió:

> We noticed that a recurring event is not communicated to the frontend
> as 1 event, but as multiple separate single events. Why did you take
> this design decision?

The only way to show recurring events on Fullcalendar implies
generating all instances for a recurring event and passing them with a
common internal id to the frontend. Fullcalendar understands them as
multiple instances of an event.

iCalcreator has a selectComponents() function that expands recurring
events, so I use it to expand them. It has some bugs (sometimes
recurrence exceptions don't get generated as they should), but it
usually works all right.

Regards.

--
Jorge López Pérez
http://adobo.org
Jabber: jorgelp@jabberes.org
_______________________________________________
DAViCal-dev mailing list
DAViCal-dev@lists.davical.org
http://lists.davical.org/listinfo/davical-dev