• A real programming language (PHP) rather than some lame imitation which doesn’t even have proper flow control structures. Of course this also means it’s very easy to set cookies, use CGI parameters etc.
• More more out-of-the-box flexibility and functionality on the backend
• Unbelievably easy to set up on my own webserver
• Over 4000 plugins! including ones for SyntaxHighlighter and Google Analytics
• Countless themes, many of which support fluid width content columns.

So I’m totally sold; now I just have to make different RSS feeds available for my different audiences (none of which exist yet…)

1. In MyTracks, copy the track to SD card as a KML file
2. Plug the phone in via USB and mount the SD card’s filesystem
3. Copy the KML file from the kml directory to a local directory.
4. Open the KML file in an editor, search for 7f0000ff (light orange) and change it to ffcc66cc (purple) or something more visible
5. Ensure the track name is correct
6. Go to http://maps.google.co.uk/ (ensuring I’m signed into my google account)
7. Click “My Maps”
8. Click “Create new map”
9. Click “Import” and upload the KML file
10. Edit the route if necessary and save changes.
11. Sometimes it’s necessary to click on another route and back to this new one, in order to make the “View in Google Earth” link appear.
12. Copy the URL of the “View in Google Earth” KML link and paste it into the Google Maps *search* bar (yes that’s right, *not* your browser address bar)
13. Click “Link” near the top right
14. Share the link with friends and/or paste the embeddable HTML into a new blog post.

The copy of the “View in Google Earth” KML link back into the search bar in step 12 is necessary to stop Google Maps from splitting the route up into multiple pages, which would only show shorter segments (“lines”) of the overall route at one time.

[Update: before you think about imitating the following approach, you should know that I gave up with Blogger and switched to WordPress which is far more flexible and easy to hack.]

Unfortunately it turns out that Blogger’s XML-based template layout system is not quite as flexible as it first seems. It’s almost superb, but has some key omissions:

• Flow control is limited to <b:if>, <b:else>, and <b:loop>. Crucially, you can’t break out of a loop.
• No writable variables of any kind.
• Conditional testing via <b:cond> is extremely limited. I kept expecting to find some comprehensive documentation for the xmlns:expr namespace (which is used via things like <a expr:href='data:blog.homepageUrl + "search/label/foo"'>), but it doesn’t exist, simply because all you can really do is simple comparisons using a limited set of data and hardcoded strings.
• There are no string-handling functions, and you can’t get access to the current QUERY_STRING to do any kind of parametrisation (for example, show some HTML saying which label you are currently viewing based on what comes after /search/label/ in the current URL).
• The box generated by the status-message includable is hardcoded to either be invisible or say “Showing label foo. Show all posts”. It cannot be customised.

I briefly considered ditching the idea of fiddling with this XML, and just using Javascript and CSS to hide the posts I wanted hidden, but persevered and came up with a solution with the following ingredients:

• I will label all posts with at least one of ‘geek’ or ‘main’, or possibly both. Posts labelled ‘main’ will appear on the default home page view. This is unfortunately necessary since there is no general way of excluding posts with a particular label, only including. The reason for this is that the only way to test for membership in a set of labels is by looping over all the post’s labels, and when you find the one you are including for, you output the post’s contents. If you were trying to exclude, you’d need a temporary variable to flag when you’d found the excluded label, then use that outside the loop.
• I used a standard template modification trick to limit visible posts on the home page to those labelled ‘main’.
• I wrapped my custom code in stuff like <b:if cond='data:blog.pageType != "item"'> so that it wouldn’t mess with single-post views.
• I figured out that http://blogs.adamspiers.org/search/label/ is a URL which will yield a view containing all posts, circumventing the <b:if cond='data:blog.url == data:blog.homepageUrl'> equality test in my default view (http://blogs.adamspiers.org/search/ also works)
• I reimplemented the status-message box from scratch, using Javascript:

  var labelsel = document.URL.match(/\/search\/label\/(.*)/);
  var view = 'unknown';
  if (document.URL == "<data:blog.homepageUrl/>") {
  view = 'default';
  } else if (labelsel) {
  switch (labelsel[1]) {
  case "": view = 'all';     break
  case "main":       view = 'default'; break
  case "geek":       view = 'geek';    break
  default:           view = 'label';
  }
  } else if (document.URL.match(/\/search.*updated-min/)) {
  view = 'time range';
  } else {
  view = 'unknown';
  }
  
  switch (view) {
  case 'all':
  document.write("Showing all posts.  <a href='/search/label/main'>Hide the geek stuff</a> or <a href='/search/label/geek'>hide the non-geek stuff</a>");
  break;
  case 'default':
  document.write("Not showing computer stuff.  You can see <a href='/search/label/geek'>the geek stuff</a>, <a href='/search/label/music'>music stuff</a>, or <a href='/search/label/'>all posts together</a>.");
  break;
  case 'geek':
  document.write("Only showing computer stuff.<br/><a href='/search/label/'>See all posts</a> or <a href='/search/label/main'>just the non-geek stuff</a>");
  break;
  case 'label':
  document.write("Only showing posts labelled <strong>" + labelsel[1] + "</strong>.<br/><a href='/'>Go to default view</a>");
  break;
  case 'time range':
  document.write("Showing posts within a time range.<br/><a href='/'>Go to default view</a>");
  break;
  case 'unknown':
  document.write("Unknown viewing mode, but don't panic.");
  break;
  default:
  document.write("BUG: Don't know how to handle viewing mode " + view);
  }
  

• I replaced the non-item part of the feedLinks includable with a hardcoded version.
• I altered the label-listing widget to exclude the ‘main’ label from being displayed.

If you want to look at my complete layout template, it’s here.