Not a major issue, but one that had caught a few people out.

At some point, I plan to get all of our CD’s onto the Viglen PC that’s sat behind the TV. When plugged into the hi-fi, it’ll make an ideal media box. It does lack one thing however; a nice UI for controlling it. This is where the Joggler can come in – and I’m not the only one to have considered it. I know others have got things like XMBC and Squeezebox running, but I wanted something that integrated better with the existing Joggler apps.

The basic idea will be to use mpd on the Viglen as a simple music server for which the Joggler will act as an client that sends commands to control the music playback.

The app will let us browse the music collection on there, pick an album/track, set up a playlist – all the usual things you’d expect.

Here’s a video of the app as it current exists running in the emulator. You can see me browse through the music, add a Coldplay album to the playlist, start playing the list, then removing tracks from the playlist. You’ll note there is no sound on this video… mostly because I’ve not yet done the connection to the server part; all the album/artist data is mocked up so I can develop locally.

Joggler Music App from Nicholas O'Leary on Vimeo.

Clearly there’s lots still to do to make it properly usable – but it has definitely been a useful way to learn more about ActionScript.

Under the covers, it already runs Linux with the entire interface built in Flash. This makes it a challenge to develop for – Linux certainly isn’t overrun with Flash development tools. After some trial and error, I have figured out the basics. So herewith a beginners guide to developing Joggler applications under Linux.

Note, this is not intended to be a Flash or ActionScript tutorial – I am not an expert. Everything you see here I have worked out from scratch this week.

Installing dependencies

1. Install swftools.

$ sudo apt-get install swftools

This provides a number of useful tools for working with flash swf files. The key one for our purpose is as3compile – an ActionScript 3.0 compiler.

2. Install a standalone flash player. I use Adobe’s own – you can try one of the open-source alternatives if you want.

3. Register for, and download the SDK from OpenPeak. This includes a complete version of the framework that lets you debug and run on your laptop, rather than have to copy over to the Joggler each time. The docs pdf included with the SDK explains how to do this in the ‘Testing Applications’ section.

$ cd SDK/published/
SDK/published$ flashplayer openframe.swf

Creating a new application

1. Create a new application directory under the SDK directory.

$ mkdir SDK/published/apps/DemoApp

2. Add an entry for the application to applications.xml file – this tells the framework where to find the various pieces.

<app static="1" id="test" loc="./apps/DemoApp/"
          icon="icon.swf" app="main.swf" />

3. In the application directory, create a language.xml file. This contains all of the translatable text of your application. Even if you don’t plan to translate your application, you must still create this file with an entry for the name to display beneath the icon on the main menu.

<copy>
   <mm en="Demo App" />
</copy>

Creating icon.swf

The documentation specifies what the icon movie must consist of – a 100×100 movie with a button. After some experimentation, I’ve got a template ActionScript file that does the job. Copy the following into a file called icon.as within the application directory.

package {
    import flash.text.TextField ;
    import flash.text.TextFormat ;
    import flash.display.MovieClip;
    import flash.display.SimpleButton;
    import flash.display.Shape;
    import flash.filters.ColorMatrixFilter; 

    public dynamic class DemoIcon extends MovieClip  {
        public function DemoIcon() {
            // Create a button
            var button:SimpleButton = new SimpleButton();
            // Setup the various states of the button
            button.upState = new DemoIconButton();
            button.downState = new DemoIconButton();
            button.overState = button.upState;
            button.hitTestState = button.downState;
            // Add a fade to the down state of the button
            button.downState.filters = [(
                new ColorMatrixFilter([1, 0, 0, 0, 0,
                                       0, 1, 0, 0, 0,
                                       0, 0, 1, 0, 0,
                                       0, 0, 0, 0.7, 0]))];
            // Add the button to the stage
            button.x = 10;
            button.y = 10;
            addChild(button);
        }
    }

    class DemoIconButton extends Shape {
        public function DemoIconButton() {
            // Draw the button
            graphics.beginFill(0x996633);
            graphics.lineStyle(2,0xffffff);
            graphics.drawRoundRect(0, 0, 80, 80,20,20);
            graphics.endFill();
        }
    }
}

Next, compile it to the required swf file:

SDK/published/apps/DemoApp$ as3compile icon.as

If you launch the openframe now, you should see the icon in place.

As you can see, it isn’t the most exciting icon. But it does have a nice fade effect when pressed. To change what it looks like, you can play around with the DemoIconButton() method – with a little help from the reference on flash.display.graphics.

Creating main.swf

I’m still working out how best to approach writing the main application. There are some parts in the documentation that simply don’t work for me – this may well be a result of not using the official Flash development tools.

The docs say the main app needs to include a class that extends op.framework.OpenFrameApplication. I found importing this class, even without using it, made the app fail to launch. Not a great start. However, it seems to work without using this class.

Copy the following into a file called main.as within the application directory.

package
{
    import flash.display.MovieClip;
    import flash.display.*;
    import flash.text.*;

    public class DemoMain extends MovieClip {
        function DemoMain() {
            graphics.beginFill(0x000000);
            graphics.drawRect(0, 0, 800, 410);
            graphics.endFill();

            var textField = new TextField();
            var textFormat = new TextFormat();
            textFormat.font = "Arial";
            textFormat.size = 30;
            textFormat.color = 0xffffff;
            textFormat.bold = true;
            textField.defaultTextFormat = textFormat;
            textField.text = "Hello World!";
            textField.autoSize = TextFieldAutoSize.LEFT;
            var tm = textField.getLineMetrics(0);
            textField.x = 400-tm.width/2;
            textField.y = 200-tm.height/2;
            addChild(textField);
        }
    }
}

As before, compile it to the required swf file:

SDK/published/apps/DemoApp$ as3compile main.as

Using the op.* libraries

The framework includes a number of actionscript libraries to provide integration with the platform. They are provided as uncompiled actionscript files under the SDK/op directory. To compile against them, as3compile needs to know where they are. Assuming you’re still developing in the application directory created earlier, then the following does the job:

SDK/published/apps/DemoApp$ as3compile -I../../../ main.as

I have had mixed success using these libraries – here are some of my findings that may help you.. or not.

op.framework.OpenFrameApplication

As mentioned previously, simply importing this class is enough to stop things working.

op.framework.OPLang

This class provides access to the entries in language.xml file. When included, I get the following compile error for which I have yet to find a workaround:

op/framework/OPLang.as:80:39: error: can't convert type String to XMLList

This currently rules out using this class.

op.framework.OPLink

This class provides the main link between the application and the underlying framework. When included, I get the following compile error:

op/framework/OPLink.as:13:30: error: syntax error, unexpected *=

This is easily fixed by adding a space between the * and = in two lines of the library:

private static var apploc:* = null;
private static var so:* = null;

Anything that imports fl.*

It appears that whilst as3compile can handle references to the core flash.* packages, it knows nothing of the fl.* ones. Haven’t found a solution to this yet.

Running on the Joggler

You’ll need a means to copy over your newly developed application to the Joggler. Start by installing telnet, then ssh and finally scp.

The install process is the same as I described before; creating a directory for the application, followed by adding an entry to applications.xml. This all goes under /media/appshop. Once in place, you need to restart the software to pick up the new app:

$ killall tango

Conclusion

As you can see, it isn’t the smoothest experience. But with some perseverance, the end results ought to be worth it.

As part of the Emerging Technologies group at IBM Hursley, Kevin gets to play with new technologies to see how they might be useful to IBM’s customers. One such item is the Emotiv headset (an electroencephalograph if you must), which can read signals in the brain. You can train it to recognise particular thoughts which has some very interesting applications from gaming to rehabilitative care. You can find out more about the headset in this piece from The Times. But I digress.

The BBC were interested in finding out more about the headset and what sort of thing IBM had been doing with it. Knowing they were interested to see if a car could be controlled by the headset, Kevin was looking for something to make the demo more relevant, which led to his tweet.

With only a couple days to put something together, I suggested we go down the route of wiring up an existing radio controlled car to an Arduino. Kevin already had the headset hooked up to MQTT, so it would be trivial to use my arduino MQTT library to get them all talking.

A quick trip to Asda and I was the proud owner of a £9 blue Mini Cooper car, which I attacked with my soldering iron. It didn’t take much to get it working – I’ll blog the finer details of that bit soon.

The demo went well and we discussed more about what they wanted to do for the programme itself. Some of their ideas were ambitious to say the least. Someone mentioned the idea of driving a bus through Whitehall… not sure how serious that was. But ultimately, a straight race between two taxis ‘driven’ by the two presenters was decided on.

A couple weeks later, they were back in Hursley to film with Jem and Dallas. Now, there are some things that are best not left to the last minute. Such as realising they needed two radio controlled cars for filming – when I only had one. Luckily this dawned on me the day before they came down so I returned to Asda and got a shiny red sports car that would look good alongside the mini. I then discovered one of the reasons they were so cheap is that both worked on the same frequency… one remote drove both cars. With time running out, I went back and got a gaudy yellow jeep that was a completely different make and thankfully worked on a different frequency.

A couple of weeks later, Kevin and I headed up to a barn in middle-of-nowhere-Northamptonshire where Jem had been working on the taxis. Now, a few people have said to me “yeah, but he doesn’t really do the work does he?”, to which I have to reply that he very much does; Jem really knows what he is talking about when it comes to building things and the enthusiasm he portrays on screen is just what he’s like in real life.

Over the course of two freezing days, we got the radio units hooked up to MQTT, again via an arduino. This was probably the piece I was most worried about – it was one thing to hack a toy remote control but it was going to be quite another to do the same to an industrial radio set that cost considerably more. Not to mention the fact that they were also on loan for the project, so breaking them would have not made me any friends.

We filmed the first test run and the relief was palpable when the car lurched forward thanks to Jem’s brain – not to mention the reaction when he managed to brake within a few inches of an oil drum. Although none of that made it into the final programme.

And then we had the main event – the race itself at the Santa Pod Raceway. 8am on a freezing December morning is not the best time to be trying to wire up the last few connections and try to debug why the damn thing wasn’t working. But somehow we got there and eventually the taxis did what they were thought to do – even if one did plow into the crash barrier at some considerable speed.

The plan had been to do two races; a straight race and an obstacle course. Technical hiccups along the way meant it wasn’t until after lunch that we got the straight race filmed, at which point we were running out of light. It was decided to put Dallas in the back of a taxi and have Jem drive him around. This was the first proper test of steering by mind-control. Let’s just say I wouldn’t enter into a slalom race any time soon.

With all the filming done we packed up and headed home. Almost 5 months later, we got to see the end result on TV. Having spent the best part of 4 days filming, I was fascinated to see how they would edit it down to the 10 minutes or so they had to fill. I have to say I’m really please with the result. They may have given Kevin the speaking part out of the two of us, but I think I got more close ups. Given the target audience, I’m also not that surprised that they didn’t dwell on the finer details of the technology.

That said, I’m a proud geek that managed to get both my Ubuntu lanyard and an Arduino onto prime-time BBC One.

Update: you can see the bits of the programme that featured the taxis here.

After what was a quite stressful, cold, but ultimately highly enjoyable few days at the end of last year, I’m going to be on TV.

Can You Train Your Brain?
Wednesday, 21st April, 21:00 on BBC One

A Bang Goes the Theory special to help you improve your brain. The science team gives the results of the world’s biggest ever brain training experiment and reveals how you can make yourself smarter.
…
Resident extreme engineer, Jem, taps into his brain to drive a car with the power of thought alone.
…

I’ll save the full story until after it airs so I don’t spoil anything – but it should be good viewing.

Back in November 2008, I spoke at HomeCamp about the Current Cost stuff we were doing as well as about the ambient orb I had made.

A few days later, on my birthday in fact, I got an email from a freelance writer who was putting together a short piece for the then soon to be relaunched Wired UK. He was writing about HomeCamp, Current Cost and all those sorts of things and wanted to feature my ambient orb. We had a chat on the phone and I gave him a brief run down of the orb, what it was, how it could be used for energy monitoring. We left it at that and I waited to see what happened.

A couple weeks later, I got a phone call from someone at Wired. Given the visual appeal of the orb they wanted to send around a photographer to help illustrate the article. Slightly bemused by it all, we organised a date and time for the photographer to come to my house and do his thing.

It was a weekday in late January 2009. I slipped out of work after lunch mentioning something about an appointment and headed home. I really wasn’t sure what to expect. I was picturing a guy would turn up with a camera, spend 10 minutes taking a couple photos and be off to his next job – the life of a freelance jobbing photographer.

When he arrived we had a quick chat about the orb, talked about various ideas for how to shoot it, and I gave him a tour of the house looking at potential locations. At this point, he went back to his car and started to unload his equipment and I got a lesson in professional photography.

There were at least two cameras and multiple lenses, two spotlights on tripods and a another pair of tripods between which a huge roll of paper was hung as a backdrop. This wasn’t going to be a brief visit and sure enough, my living room was turned into a makeshift studio for the next 2 hours.

And it wasn’t limited to that – we moved up to the spare room with my desk as well as half an hour spent in the kitchen. The search for the perfect shot was relentless. Ultimately it would be up to the Wired UK guys, but he wanted to make sure they had lots of options.

In an attempt at small talk, I asked if he did this sort of thing often. He said that being based in Brighton (yes, he had driven over from Brighton for this – I did wonder at that point why Wired hadn’t hired a more local photographer…) he tended to do music based shoots. I’m glad I didn’t follow that up with a ‘anyone I’d know?’ type question…

After he left, I decided to google him, Alex Lake, and I found his site Twoshortdays. It was about this point I suddenly flashed through my head everything I had said to him to make sure I hadn’t been a tit. Go and have a look. You see, his other jobs have included some great portraits of people like Amy Winehouse, Guy Garvey, Boy George and Bob f’ing Geldof. There are dozens of portraits of very famous people on there – and he was in my living room, helping me move my sofa so we could take some photos of my little ambient orb.

Did I mention Bob f’ing Geldof?

On top of that, he’s also an illustrator. The odd little doodle? No. He designed a number of Keane’s albums – including Hopes and Fears.

Did I mention I asked him “so, are you a freelance photographer then? Or is this just something you do on the side?”

Anyway.

It would appear the article got spiked in the end – it still hasn’t surfaced in the magazine and I can’t believe they would have held on to it for this long. I did email Alex late last year in case he had any photos from that day without any reply.

Bob f’ing Geldof.

And that is how I almost got into Wired UK.

A single, solitary Kestrel, stalking its prey.

A thousand Starlings, coming in to roost.

Over tea with Andy a few weeks ago, we managed to place our collective fingers on a basic problem with ambient orbs like this; whilst they may be capable of displaying any colour, the key thing is they can only display one colour at a time – they are a single channel of information.

For example, if I used blue to signify new messages for me on twitter, what should the orb do when my energy goes over 500 watts and someone has @knolleary’d me? The orb could alternate between the two colours, but that would feel too distracting for what is supposed to be an ambient device. A third colour could be defined for this combined state, but that wouldn’t scale very well.

This train of thought brought us to identify what it would take to have an ambient orb capable of displaying more than one piece of information at any time. When put like this, the answer is fairly obvious; have an orb that can glow more than one colour at any time. An evening of soldering later, here’s where I got to.

The orb has three RGB leds in it that are individually controllable. When they all show the same colour, the orb is a solid colour, but when they are different, the orb displays multiple colours at once.

This one doesn’t use blinkm’s for the simple matter of cost – I found a supply of the leds on e-bay that got me 50 for £15 – although this does mean I need to implement fading between the colours.

The plan is to put a small controller in the base to drive all the leds – for now it’s plugged straight into an arduino.

I think it’s only fair to put in a spoiler alert at this point; I can’t guarantee that the rest of this post won’t reveal details of the (paper-thin) plot. Although, of course,

Back to this actual book I’m holding in my hands – well, I was before I started typing. All I know is that it once belonged to my Gran and recently reached me via my parents. Before that, it belonged to one “Gioladys O Williams”. How do I know this? Well she kindly wrote her name in it. Now, I consider myself an expert in reading English having had 28 years of practice, but that first name certainly has me puzzled – “Gladys” maybe, but “Gioladys”?

Update: Adrian kindly points out below that it’s “Gwladys”. Considering the fact “Gwladys” wins in a google fight with “Gioladys”, I suspect he’s right. In fact, now he’s pointed that out, I can’t read it as anything other than “Gwladys”.

The book starts out telling how John, our first-person-protagonist (FPP) spots an announcement in a paper that a Miss Ellen Content is returning by sea to New York. For reasons as yet unexplained, he becomes determined to get to New York ahead of her. He convinces his editor to fund it as a writing assignment – the Content Assignment. It has taken all of four pages for the title of the book to be fully explained. Magic.

Straight into chapter 2, where the fun starts. Whilst flying, John thinks back to how he first met Ellen Content. Taking us back to Berlin 1948, the scene is set in a city whose “de-nazification was almost complete in the British and America zones, proceeding slowly in the French zone and almost not at all in the Russian zone.” This is the first indication of when this book was written; clearly the Russians are in for a rough ride.

This brings me to why I’ve bothered to write about an otherwise forgettable book; its former owner, Ms Williams, didn’t stop at just writing her name inside the cover. Oh no – she did much more.

Clearly she has taken exception to the tone of the book, but what amazes me is that she kept going…

At first I thought it was the negative portrayal of the Russians that had upset her, but on the very next page she shows her disdain isn’t limited to that.

Bearing in mind this book is written in the first-person, it’s hard to tell who these comments were directed at; the author or John The FPP.

Up to this point, the comments have all referred to specific bits of text. It takes until page 38 for the dam to break and Ms Williams to write what she really thinks.

I bet she felt better for that – although it isn’t clear from her continuing stream of comments. One noticeable change is that no-one is safe from her pen. First up, are Britain’s security services and police.

You know she means business; she’s signed her name.

In a shocking turn of events, she goes on to agree with something in the book.

But she doesn’t let that deter her. New York build regulations are a surprise entry in her hit list.

She must have tired at this point, as her next comment is a single word which isn’t entirely obviously what her point is. Perhaps the irony of John The FPP feeling the part of something strange; the book itself.

Again Ms Williams can’t quite decide who she is venting at – insulting the poorly written character or the author of said poorly written character.

Towards the end of the book, she returns to her favourite subject

and again makes a dig at the quality of the writing.

In the final pages, she decides to stop holding back and say what she really thinks.

I hope they get the message – Ms Williams does not like it. I almost wish she left it there, but she ends with this.

I can hear her manically laughing as she put down her pen, closed the book and felt incredible pleased with having set the world to rights.

This is what people did before Have Your Say existed.

Wow. Simply wow.