I’ve just started shaving a goat, or yak, or whichever the ungulate of choice is this season. These are my steps so far.

1. Trace out an API in MXML .
2. But I can’t do that, because MXML won’t let me do what I want (yet).
3. Master writing AS3 for building in MXML
4. But I can’t do that, because I can’t find any references on the subject and none of my experiments have worked
5. Write a blog about it.
6. Yep, I can do that…

Read the rest of this entry »

My last talk at Flash Brighton was (for me) a discussion about how other people used state machines in as3, basically because I was dissatisfied with the limited way that I was using mine.

It turned out they used theirs in pretty much the same way. As a backbone for simple staged processes such as bootstrapping, asset acquisition and shutdown.

And that was it.

I was a bit frustrated, my original intent for using a state machine was to completely model my controller, so I would have a map of processes through out the entire application. But I kept on hitting the same problems preventing me from doing this.

Coming out of the talk, I decided that I would set myself a challenge: to change the way I used my state machine, and map all my commands through it.

I succeeded (eventually).

In this session I shall highlight the problems involved and the very simple changes of perspective it took to overcome them.

8th June
7.30 pm
dotBrighton
the skiff
tickets

I’m giving an introductory talk at FlashBrighton about State Machines on March 9th at the Werks. You can also catch it streaming live at http://live.flashbrighton.org at round about 7.00pm GMT (ok, it might not start till quarter past, when the bods in the real world have turned up :).