Hi all,
Sometime last year there was a thread about adding a caldav backend to the calendar plugin provided by kolab. Does anybody now whether there have been any progress with this?
If there have been some progress does anybody know where to find the code for this backend?
If no progress have been made or if nobody is working on this I will start implementing this backend ASAP.
To be recognized by the calendar plugin I must do the following?
Anything else I need to do?
On 01/17/2014 12:48 AM, Michael Rasmussen wrote:
Sometime last year there was a thread about adding a caldav backend to the calendar plugin provided by kolab. Does anybody now whether there have been any progress with this?
Ask on Kolab developers mailing list.
If no progress have been made or if nobody is working on this I will start implementing this backend ASAP.
To be recognized by the calendar plugin I must do the following?
- Under drivers add a folder say caldav
- In that folder create a file named caldav_driver.php
- Create a class named caldav_driver extending calendar_driver
- Implement all abstract methods in calendar_driver
Anything else I need to do?
Currently plugin allows only one driver at a time. So, if you need e.g. both database and caldav drivers, you'd need more modifications.
On Fri, 17 Jan 2014 08:14:35 +0100 "A.L.E.C" alec@alec.pl wrote:
Ask on Kolab developers mailing list.
I have now send the same post to their mail list.
Currently plugin allows only one driver at a time. So, if you need e.g. both database and caldav drivers, you'd need more modifications.
Well, as a first proof of concept I will not address this limitation. I actually have no need for two different calendar systems either so I might never address this issue. What usecase do you see for maintaining two different calendar systems at the same time?