Mapping of The Far Side of the World Complete

My map of the events in The Far Side of the World is complete. Most of the voyage was replete with references to well known rivers, capes, islands and atols making this map easier than most. I am probably least happy with the back and forth around Valparaiso (where I tried to stay true to the references in the book but was left feeling unsatisfied with the results) and the last dogleg around the prodigious storm that hit the Surprise directly after Jack and Stephen's rescue.

It has been six years since I last read The Far Side of the World and I had forgotten much and thus enjoyed mapping this volume all the more. Completing this map in ten months means I am beating my average by a couple of months and am now on track to finish the series in a bit under seven years. Hurrah!

Permalink - Comments - Tags: Patrick O'Brian,Books

CLGeocoder is not an Opera fan

I realise that Reverse Geocoding is a pretty tricky problem and probably will always be a work in progress, but the CLGeocoder bug I found today was so amusing I had to post. Things like this make this API less useful than it otherwise could be.

One of these is not the Sydney Opera House:

I built a quick test app demonstrating that CLGeocoder thinks "Opera House, New South Wales" is a suburban bungalow.

Permalink - Comments - Tags: Development,iPhone,iPad

Four months later and I still suck at this game

Four months of indie game development in under three minutes.

Permalink - Comments - Tags: Development,iPhone,iPad

WordFlight

The Classic 'find a word' game reinvented. Compete with your friends and the world.

Free to play with no advertising. Upgrade for more challenging games and word lists.

Permalink - Comments - Tags: Development,iPhone,iPad,App

Select a device with min API level <x>

Had a frustrating hour or so today trying to get Eclipse to run goCatch on an old HTC Desire running Android 2.2. Eventually found the solution so this is a note to self to avoid this in the future.

The problem was that old device was not showing up in the Android Device Chooser, who (notice how I anthropomorphize pretty much everything?) smugly asserted Select a device with min API level 11. This sent me into a little bit of tailspin because I had jumped feet first into moving over to Android Maps V2, ActionBarSherlock and Support Library goodness with the understanding that I could support devices all the way back to 2.2. I frantically went through all the dependencies I had recently introduced, looking for a minSdkVersion greater than 8 (Android 2.2). To my relief I didn't find any. I double checked my own manifest and made sure my minimum API was set correctly. It was:

<uses-sdk android:minSdkVersion="8" android:targetSdkVersion="17"/>

What the hell?! Why is the device chooser insisting I could only run on devices with API level of 11 or more? I dug through about a thousand (might have been less than a thousand) config screens in Eclipse looking for a obscure project property that was causing the issue, with no luck.

Eventually I decided I would reduce the targetSdkVersion down to 8 and see if I could build and run on the old device. I updated the manifest and did a clean build for good measure. Eclipse built my project and ran it on the device. Android Device Chooser was now happily insisting that I should Select a device with min API level 8.

Not really wanting to target API 8, I udpated the Android Manifest back to its original state and voila everything works. Hooray!

Permalink - Comments - Tags: Development,Android,Google

[First Page] [Prev] Showing page 4 of 6 pages [Next] [Last Page]