dale lane

I mentioned last week that watching Doctor Who made for a good chance to absentmindedly play with some code. I seem to have started a new habit, so thought I’d share what I was worked on this week. 🙂

One of the problems with my HTC Universal is running out of storage space when trying to install new apps. The core Windows Mobile 5 tools that you can use to work out why you’re short of space are fairly limited:

• Search – listing all files on the device larger than 64KB (an odd size to choose – and without the ability to specify which folder(s) to search in, you end up with a very long list)
• File Explorer – shows file sizes and lets you sort a folder’s contents by size (but going through each and every folder on the device manually is fairly tedious, and there is no way to get the size of a folder without adding together the size of the contents yourself)
• Memory applet – showing you how much space available and how much in use (useful to identify that you have a space issue, but not any use in working out why)

You often just look around and rely on trial-and-error to free up space. (Like clearing the Pocket Internet Explorer cache then finding that you have a big chunk of space freed up.)

The aim for yesterday evening was to produce something to visualise the usage of storage space on the device.

Not a terribly original idea (basically a simplified approach to drawing a tree map), but unless my ability to use Google is getting worse, I don’t think anything like this is available for Windows Mobile at the moment.

I think it might be a useful little app, and it only took a bit of an evening to throw together. 🙂

If you’re curious, read more to see some screenshots and a quick description of what I did.
(more…)

People keeping half an eye on my Wakoopa feed might have noticed that I started playing with RAPI Start this weekend.

RAPI Start is a command-line tool that lets you remotely run commands on a Windows Mobile device from a connected desktop. It’s quite neat, so I want to see what sort of things I can do with it.

Here is noddy first attempt number 1 🙂

The problem:
I get a text message while I’m sat at my desk with my mobile connected to my computer. (For a mobile device, it spends a large amount of it’s life tethered to a desktop – but that’s a discussion for another time!)

I want to reply, but writing on a mobile device is fiddly. I’m sat at a full-sized keyboard, so why can’t I just use that instead?

(more…)

Can’t sleep.

So I thought I’d go back to some of the Google Maps API stuff I last played with about a month ago.

The Google Maps code I wrote before would show my last stored location.

I thought it’d be more interesting to see a number of updates over a period of time – so went back to the code and tweaked it to show updates from the last day, week or month.

• day
• week
• month

Code is a bit messy, but in my defense it is past midnight 🙂

I wanted to use the Google routing algorithm used to show directions – to link together the points that I have been to over time. Assuming that I will probably have taken the most direct route between points, then you would end up with something approximating my travelling over time.

Unfortunately, Google don’t expose their routing stuff in the API. Shame.

And on a related note, apparently if I’d used the Yahoo Maps API to do all of this, I’d be breaching their terms of service.

A friend sent me this:

You may use location data derived from GPS or other location sensing devices in connection with the Yahoo! Maps APIs, provided that such location data is not based on real-time (i.e., less than 6 hours) GPS or any other real-time location sensing device, the GPS or location sensing device that derives the location data cannot automatically (i.e. without human intervention) provide the end user’s location, and any such location data must be uploaded by an end-user (and not you) to the Yahoo! Maps APIs.

Spoilsports! (Well, I guess it’s more to do with the demands of who provides their mapping data, but pah – yay for Google)

Note: This post is a bit thin on content – sorry about that. But Twitter is down, so had to say this somewhere! 😉