3 ms·
This is great, I was looking for something similar when I was in org-gcal mode last year. I'll have to revisit this link
by kfrzcode 10y ago
This is great, I was looking for something similar when I was in org-gcal mode last year. I'll have to revisit this link
- kxyvr 10y agoThat does indeed look neat. At the same time, there are extensions to CalDAV that codify how to add scheduling to the standard. Namely, RFC 6638: https://tools.ietf.org/html/rfc6638 https://tools.ietf.org/html/rfc6638 Certainly, it's something that I wish khal had. This is why I think I'm missing something. Certainly, dealing with CalDAV is a pain because many programs don't produce standards compliant files. That said, it really just looks like a CalDAV server has a folder with a bunch of text files that contain the calendar information. If I want someone to have view only access to that folder, they have read access. If I want someone to have the ability to add calendar events to my schedule, they have read/write access. The file uploads look like they use WebDAV. Syncing across devices just means syncing to the folder on the server. Exotic calendar tricks can be handled either from a server side script or a client side script followed by a sync. Now, I wish that were easier and I think there's room for improvement especially in developing a language to make it easier to write these scripts. However, is there really something fundamental that this framework doesn't have that these other calendar programs provide?