Tickets :: Comment on [#3032] WebDAV / iCal support for Kronolith

* Your Email Address
* Spam protection	Enter the letters below: .__ .__ .__..___.. . [__)[__)\| \| \| \|\/\| \| \\| \|__\ \| \| \|
Comment	> Ah, that's nice :) > > > > Currently, I have two ideas for building the webdav/ical support into > this. I can add files with the name calendar.ics in the listing of > kronolith (so you get something like the following): > > > > calendar_name/ > > calendar_name.ics > > other_calendar/ > > other_calendar.ics > > > > Or another solution is seperating it into different parts of the tree > structure: > > kronolith/webdav/calendar_name.ics > > kronolith/caldav/calendar_name/ > > > > I've also looked a bit more into to CalDAV, but the problem of > putting events seems rather simple. First, you have to put it into a > existing calendar directory. If you want to put it into a new > calender, you first have to create a new calendar with MKCALENDAR > (part of the CalDAV spec), and then put it into the folder which is > created with the MKCALENDAR command. > > > > For adding calendar's with WebDAV, it should be simply creating a > calendar with the (part of) the file name (so calendar_name for > calendar_name.ics). After this, the data of the file can be imported > (or does the import already create a new calendar if it doesn't > exists?). > > > > I think it is still necessary that the Horde WebDAV class uses some > registry function for PUT, so it is possible to call the import > function with the necessary parameters. I don't see how this could > really be solved using the current browse function. > > > > Just another question, how mature is the CalDAV support, or is it in > it's current state nothing more that getting events?
Attachment
Watch this ticket

Saved Queries