Katie was managing 4 or 5 different versions of calendars between her iPhone, Mac, and Google Calendar. It was leading to dupes (and trips!) of things showing up and just making a general mess. So I thought I would help. I get everything reduced to just a couple of calendars synced to iCloud.

Then I go to move her Google Calendar to iCloud like I did with my own GCal. I export her ics file, import it into iCal, and merge it into her normal calendar.

Everything looks normal.

Until iCloud starts sending out acceptance emails to people for meetings from her work calendar (that had been synched with Google Calendar back in 2008 and 2009).

Yep, tens, maybe hundreds of acceptances to meetings that were years old. I’m sure there’s a setting that I missed somewhere, but that just doesn’t seem like the right thing, Apple, now does it?

 

There’s a lot of awesomeness about Google Calendar. I’ve been using it, synced to my iPhone, iPad, and Mac, for pretty much everything but my work calendar (stupid Exchange). I used it so much that I even built a Greasemonkey script to automatically create Google Calendar entries from Evites. That’s not necessary any more (Evite finally added it natively), but it’s safe to say I used Google Calendar pretty exhaustively.

Over time, working with Google Calendar across all those devices became a bit tougher. It’s not really Google’s fault–I just wanted to do some stuff that wasn’t as easy to do. Syncing across multiple devices with all of them being able to read/write/update entries became a crapshoot as to whether or not an update would work. Weirdness with iCal (on the Mac) where all of a sudden it couldn’t authenticate to Google’s servers. I’m not sure where the fault lies (probably both on Google and Apple: Google tends to do some stuff non-standard; Apple seems to sometimes not handle non-standard stuff very well), but it would go flaky every now and then.

That being said, it still worked very, very nicely. Mostly. iOS 4 made it even easier when they added native Google Calendar syncing.

But, in iOS 5, Apple released iCloud, and with it, the chance to simplify a bit. I could drop some of the workarounds to go native Apple. So, as risky as that sounds (remember MobileMe … or hell, remember the trouble just downloading and activating iOS 5?), I decided to bite the bullet and move my calendar out of GCal to iCloud. Just one less thing that could go wrong…for better or for worse.

Google makes it very easy to get your data out. Within a minute, I had downloaded my .ics file with all of my historical events. Over to iCal, import, and boom.

It would fail every time.

After a bit of digging (using Console.app), I could see this error:

iCal: Component boundaries mismatch (VALARM VEVENT)

That lead me to think that maybe Google’s ics file had some sections that didn’t match right (I’m pretty smart, eh?). Thanks to Google’s search engine, I was able to figure out why Google’s Calendar wouldn’t give me my data.

I uploaded my ics to this iCalendar validator. I helpfully told me places where the file didn’t parse properly. Using my favorite text editor (hosted on Google’s code repository–is there anything these guys don’t do?), I fixed the problems.

Voila. Everything imported nicely. Moments later, I had my calendar on iCloud.com, on my phone, and on my iPad. Working exactly the same as it was before, but now I get to more easily take advantage of some of Mac OS’ and iOS’ niceties (data detectors, applications creating calendar events), and I can to take one “sync” out of my chain.[1]


  1. Unless of iCloud craters and I go rushing back to Google.  ↩

 

With the holiday season upon us, I got a few Evites that broke my Greasemonkey script to add Evite invitations to your Google Calendar. I went through and cleaned up the code a bit, and I think it’ll work a bit better now.

You’ll find the “Add to Google Calendar” link next to the Print link on most invites.

Evite2GoogleCal.user.js v1.2

 

There’s lots of little things that, if tweaked, would just make life a lot nicer . . .

For instance . . .

The Google Calendar sync tool should support syncing Outlook to secondary Google Calendars, not just your primary calendar. That would mean I could drop SyncMyCal which runs in my Outlook-only Parallels Virtual Machine. I’d have a nifty, no-click workflow to sync my Work calendar to my secondary Work Google Calendar, which get sync’d down to iCal and to my iPhone.

Better yet . . .

The iPhone should support syncing both iCal and Outlook calendars. It’s sort of a dumb thing that if you turn on Outlook calendar and contact syncing, that’s the *only* calendars and contacts you get. Why not keep them separate? If Apple added the ability to have your Outlook calendar sit right along side your iCal calendars, then I wouldn’t even need to sync my Work calendar up. I could just accept meeting invites on my phone and have everything work nice and happy.

Oh, and same goes for Contacts. Just let me sync my Exchange contacts as a separate group. Seriously.

Even better . . .

Apple Mail and iCal should build in real Exchange support. Then I could actually not run Outlook in my virtual machine all day. Instead, I could just use Mail and iCal as Exchange clients and have the most simplified workflow of all. Supposedly, this is going to happen in Snow Leopard. That would be awesome.

Making life even sweeter . . .

Google should fix contact management. I love Gmail. I use it for everything. I hate Google’s Contact stuff. It is awful. They tried to make it better. It didn’t work very well. But they’ve got the keys right in their hands … Social Graph. Imagine you gave Google some information about you that they could use some OAuth or other authentication means to determine that it is really you. So you hand them some keys to Flickr and Twitter and (if they can work out their differences), Facebook. Now, Google pulls all that information together and makes a nifty contact for you. Name, picture, email address, home address, work address, phone number, Twitter, Flickr, etc, etc. You only get as much information as the contact allows (if we’re not friends on Facebook, you don’t get my phone # or address).

Now, Google can do all this behind the scenes and give you a little button to “add so-and-so” as a contact. If I add them, they go into my Contacts section. Then, I subscribe to my Google Contacts like they’re an LDAP source or however else they want to get hooked into your setup.

Boom. All of a sudden I’ve got a real contact solution that’s continually updated.

Ok, sure, that’s a lot like what Plaxo promises. Except Plaxo really doesn’t work all that well.

So. When all this happens, I’ll have my calendars all seamlessly syncing together to my computer and to my phone. On top of that, my contacts (work and personal) will all sync nicely as well. And stay up-to-date, thanks to something like Social Graph or the like. Plus, Snow Leopard will mean I don’t have to run a Virtual Machine just to use Outlook (and don’t tell me to use Entourage … it barely works).

With my work life (and personal contacts) working so seamlessly . . .

I’ve got time to kill. I want to get through some movies or TV while I’m out and about.

Give me Netflix Watch Instantly and Hulu on my iPhone! Now that they’re on my XBox and Mac, I’d love them remotely. When I’m out eating lunch or riding in a car, I don’t need HD video. I just need crappy streaming video that will let me knock off an old episode of Newsradio or watch 15 minutes of a crappy movie.

But, if I don’t want to watch something . . .

Sometimes I just want to listen. The fact that the new version of the iPhone firmware lets you download podcasts is great. By why doesn’t it sync my entire podcast list and let me just quickly scan for a new episode of something I listen to? Even better, why not do something similar to Genius and recommend me a podcast I might like?

All that would be very cool.

Oh, and why can’t I sync stuff over bluetooth. That would be good too.

 

So, Google announced recently that it would support CalDAV syncing with iCal, which means if you update an entry in iCal (or Google Calendar), they’ll be in sync within a few minutes. Awesome.

Unfortunately, it meant that my previous script iteration would now continually add alarms, leading to each entry having 3 or 4 alarms. Turns out that updating a local iCal calendar and adding an alarm actually updates that same info at GCal. Which is awesome (but was unexpected).

So, I made a small tweak to the script, which makes it run a bit faster and makes sure that you only get one alarm on an entry:

Try this instead:

tell application "iCal"
  set theCalendars to {"Cal1", "Cal2"}
  repeat with theCurrentValue in theCalendars
	tell calendar theCurrentValue
	  set theEvents to every event
	  repeat with theCurrentEvent in theEvents
	    tell theCurrentEvent
	      if not (exists sound alarm of theCurrentEvent) then
		   make new sound alarm at end /
		   with properties {trigger interval:-15}
		  end if
	    end tell
	  end repeat
	end tell
  end repeat
end tell

That basically means it won’t add another sound alarm if the entry already has one. Much handier. In fact, you could just take that script and have it run every few hours (either cron’d or via iCal), and not have to worry about the iTunes Sync script.

© 2011 That Not So Fresh Feeling Suffusion theme by Sayontan Sinha