Thanks to Eric for point out that the two marbles solution I presented previously isn’t optimal. I’m pretty confident that allowing the first pass windows size to vary will fix it up, but haven’t found the time to site down and work it through.
On the other hand, it crossed my mind this morning that the question didn’t state what we should optimise for. I imagine the number of marble drops is what’s expected, but if you took into account the running up and down stairs involved that may well affect the solution…
Yes, yes, I’d much rather see a proper API with access to the hardware for the iPhone instead of an Ajax one, but at Google’s devloper day, they claimed Safari support would be released for Google Gears very soon.
If Safari on the iPhone supports Gears, the Ajax only limitation seems a lot less limiting (even if it means we’ll never have Skype). Lots of people seem very upset about the idea that widgets on the iPhone will only work with a network connection, but gears should pretty easily circumvent that limitation.
That said, I’m not too hopeful if it doesn’t support flash movies. That, and, it will probably go through a revision or two before we can get them here in Australia anyway.
Technorati Tags: iPhone, google, gears, api, apple, safari, ajax