Calendaring… the final frontier. Not really, but probably my next next project. Seeing how far I can push iCal for pubsub, calendar sharing.
- Jon Udell: The calendar fiasco
- Ray Ozzie asks on iCal in XML – see xCal (abandoned), RDF-iCal, Jabber/iCal, SyncML
- iCal Redux 2003
- Once more into the Breach: Calendars, Events, and RSS
- iCal Web Parity without .Mac – Kellan proposes a 3-file hack, I’ll talk about my variations
- Design Notebook: pub/sub and iSync
- PHP Webdav Client Class 0.1.1 (fm
- PHP WebDAV Server Class
- iCal / WebDAV / PHP iCalendar – french, here’s the systrans
Structure: ‘entry’ calendar which will talk to PHP webdav server connected to phpMyCal. This will then generate a ‘combined’ calendar which will be subscribed to. Now here’s the neat card trick. The combined calendar is what we really want, but it’s read only (thanks a lot iCal). So… run a script (AppleScript or shell script, either through cron or if possible, triggered by update) to move the output calendar and overwrite the input calendar (also, just leave it unchecked so you don’t ever get double display). Since we’re using a PHP webdav, we can do smart diffing supa-easily on the server-side. That and authorization, etc will all be handled courtesy of the phpMyCal (input and output will be via PHP). Events are tracked by UID. Does this work?
Seems to be a 99% solution. That is, at the end of the day, you get completely synchronized, fully editable calendar. It’s about a 95% solution for group calendaring. You can set editing restrictions on the server side, but it won’t be enforcable on the client side, however, you can either make it visually locked (make a note, or put it in the title), or just send those to a second subscribe only calendar. Different privacy/control levels can be handled on a by calendar basis w/ a web config, or w/ keywords…