catch up with anti

Well, I’ve just got through a busy patch work-wise, with no time to work on any private projects, so I’m afraid the FSMVisualiser hasn’t progressed at all since my last post a while back.

However, I thought i’d post some stuff that I’ve been working on. One of these projects is a flickbook navigated trail commissioned by ANTI – Contemporary Art Festival in Finland. The work is by word picture studio (festival entry here). My part was to composite and make ready all the final prints using AfterEffects, Photoshop and InDesign.

Below are some choice thumbnails, because I sort of like looking at the flickbooks this way:

Flick the First
Flick the First, Flickers, ANTI Festival 2009 by word picture studios

Flick the Fifth
Flick the Fifth, Flickers, ANTI Festival 2009 by word picture studios

Flick the Sixth
Flick the Sixth, Flickers, ANTI Festival 2009 by word picture studios

Flick the Eighth
Flick the Eighth, Flickers, ANTI Festival 2009 by word picture studios

FSMViz Version 0.4

FSMViz for pureMVC StateMachine Utility

FSMViz for pureMVC StateMachine Utility


source code here:
http://puremvc-utilities.googlecode.com/svn/tags/fsm_viz_0.4

Added the decode to AS3.

OK, so next I’m going to rip this all down and re-architecture it.

  • create a shell and a deployment agnostic module
  • split up the encoding/decoding and parsing of the data from the data editing
  • take all the manipulation of the visualisation from the view so that the view just fires notifications
  • make the visualisation into a module so that it can be changed easily
  • add preference data so that properties can be changed easily
  • oh, and implement an FSM :)
  • FSMViz Version 0.3

    FSMViz for pureMVC StateMachine Utility

    FSMViz for pureMVC StateMachine Utility


    source code here:
    http://puremvc-utilities.googlecode.com/svn/tags/fsm_viz_0.3

    OK, so I’ve added the ability to open from JSON or XML and also to decode to them. Originally, I was just going to save out to JSON as the main “file-type”, and export to an AS3 file, but after Jason MacDonald suggested it would be good to export/import the xml, I thought why not, it only took an hour.

    The only things to note are that the XML looses all the meta data that the JSON preserves. And secondly, because of this, it can only import XML that uses the naming conversions outlined below.

    Naming convertions:

  • States will have all white spaces removed and have title case. Thus “Data aquisition” becomes “DataAquisiton”
  • Actions will have white spaces removed and have camel case. Thus “Acquisition failed” becomes “aquisitionFailed”
  • In addition to the above a prefix will be added to further define the name:
  • State names will have the prefix “state/”. Thus “Data aquisition” becomes “state/DataAquisiton”
  • Action names will have the prefix “action/”. Thus “Acquisition failed” becomes “action/aquisitionFailed”
  • Entering notification names will have the same name as their associated state, but with a prefix “entering/”. Thus the entering notification name for the state “Data aquisition” will be “entering/DataAquisiton”
  • Exiting notification names will have the same name as their associated state, but with a prefix “exiting/”. Thus the exiting notification name for the state “Data aquisition” will be “exiting/DataAquisiton”
  • Changed notification names will have the same name as their associated state, but with a prefix “changed/”. Thus the entering notification name for the state “Data aquisition” will be “changed/DataAquisiton”
  • I think that these are pretty uncontentious with the exception of the choice of delimiter for the prefix. This I think will be changable by the user.

    All I have to do now is that all important conversion to an AS3 file, then I can rip the whole thing apart and rebuild it.

    So, any suggestions as to deployment? Air, online with php service?, Zinc? (Zinc? LOL only joking!)