The good news is, I found a way to have bi-directional synchronization between Google Calendar and Apple's iCal! The bad news is, it only works for one calendar, and of course I have more than one in both places. The software to pull this off is GCALDaemon; I used version 1.0 from 2006-12-23. I've included some Terminal commands with the steps below to make it easy.
- download the Unix-compatible version and unzip GCALDaemon into
/bin(paths are hard-coded, so it needs to be
/binso you'll need to use
/bin, and you'll end up with
sudo unzipdrag-and-drop gcaldaemon-linux-*.zip file on Terminal
- change all semi-colons in
/bin/GCALDaemon/bin/standalone-start.shto colons at least for version 1.0
cp password-encoder.sh password-encoder.oops
tr ";" ":" < password-encoder.oops > password-encoder.sh
cp standalone-start.sh standalone-start.oops
tr ";" ":" < standalone-start.oops > standalone-start.sh
- put a colored label on all folders in
open ~/Library/Application\ Support/iCal/Sources
- launch iCal, and create a new calendar, maybe named Google
open -a iCal
- quit iCal, and see which folder doesn't have a label in
~/Library/Application Support/iCal/Sources(you can't go by timestamp since all calendars will be updated by iCal, but colored labels will show you the new folder clearly)
- follow the directions for file-based synchronization like Rainlendar
- put the full path to
corestorage.icsin that new, unlabeled folder (like
/Users/nethope/Library/Application\ Support/iCal/Sources/C00EE8A4-C0C1-EDC5-AA52-6AEC88F8D30B.calendar/corestorage.icswith no
/bin/GCALDaemon/conf/gcal-daemon.cfgfor the variable
- put the full path to
I submitted a SourceForge bug report about the colons versus semi-colons error, so it might be fixed in version 1.1. In that case, the
tr commands above to replace semi-colons with colons won't have anything to change in the two scripts, but shouldn't break them either. (You can always skip that step, and come back to it only if you see Java errors when you run those scripts.) According to Java documentation, "a class path may include several paths, separated by a semicolon (Windows) or colon (Unix)", so it's just a simple platform translation issue.
My backup plan, if GCALDaemon didn't work, was to try GCalSync and to have my Palm OS Treo be the intermediary to translate between Google Calendar and iCal. I don't know if that approach allows multiple calendars; if it does, then I would prefer it. I sync my Treo to my Mac with The Missing Sync specifically because I want to have multiple iCal calendars on my Mac that are also on my Treo, and I outgrew Palm Desktop a while ago (don't get me wrong, that's a good application too, but it doesn't have as many external choices to create a new event without leaving the current application).
My other backup plan was ScheduleWorld. It looks really interesting since it supports pretty much anything that stands next to a standard, and it might be a better solution. (Although I wanted to avoid needing another server, like the GooSync service.) It seems like this ought to be a simple process, an internet-connected Mac with access both to iCal and to Google Calendar, both of which talk the iCalendar standard. Who needs an intermediate server? Who needs a translator?
I guess I like GCALDaemon (for the moment) because it allows iCal and Google Calendar to talk directly. In my backup plans, I would either use Treo+GCalSync or ScheduleWorld to translate between two applications that both use RFC 2445. Why translate? Just connect 'em. Stay tuned to this channel when I put
launchd (probably with Lingon).
My setup: PowerBook G4 (almost two years old) running Mac OS X 10.4.8 (current) with iCal 2.0.3 (also current), Gmail (I don't know if a plain Google account works), and Google Calendar.