March 12th, 2004


Calendaring hatred

Considerably long ago, Computing Services used "Synchronize" for calendaring. Collapse )

Fast forward a while. Corporate Time got Kerberos 4, and then GSSAPI. I got a Mac, and the Mac client, unlike the Linux client, doesn't die immediately upon startup 100% of the time. So, now I at least try to play along. But, it's not well-integrated with other Mac applications, and it's big and clunky.

Fine, so I revisited an idea I had previously: take the Oracle Calendar SDK (Steltor got bought out by Oracle) for Mac, and write something that will let me manage my CorpTime calendar from iCal. After some research, I think I can "subscribe" iCal to a copy of my CorpTime calendar, "publish" updates back, and have a special server which correlates these and both pushes changes back to CorpTime and leaves the updated version in the calendar I'm subscribed to. The problem lies in the fact that the "published" calendar will have duplicated events, and if the event changes from the CorpTime side, I can't even see they're the same anymore and mentally collapse away the event.

Fundamentally, iCal is too simple. It's really just designed as a tool for a single user, not as a collaboration tool. The "publish" and "subscribe" modes are really just "export" and "import" on a schedule with previously defined locations. But, if I want to go forward, perhaps I can scheme a way to allow some sort of event to trigger an AppleScript to reimport the calendar I "publish" from the calendar I "subscribe" to.