I was inspired to investigate this topic by Derek Wischusen’s post “method_missing in ActionScript.”  I saw it and immediately set out to build a port of ActiveRecord to Actionscript.

I’m not convinced this is the “best” implementation for this type of functionality but after much toying about it is the best one I was able to come up with.  Also, you have to remember you can’t eval anything in AS3, so in reality this is just creating Static Methods that point to an existing method that knows how to do something based on the new function’s name, but that’s pretty much what the Rails framework does so, I view that as just fine.

Goal

The initial goal was to set out and get a method like this to work:

The class “Blog” should have as little, preferably no, extra coding in it.  It should just attempt to call that method with no burden on the programming trying to create the class “Blog.”

Strike One

The first place to start is with Derek’s post that I referenced earlier, I created a class called “ActiveRecord” that was the same as his “BaseProxy” class.

ActiveRecord v0.1

The above code is taken from this “method_missing in ActionScript.” 

Then I subclass “ActiveRecord” to get a class called “Blog.”

Blog.as v0.1

TestApp.mxml v0.1

To even get the above syntax to run you have to go to Project->Properties then Flex Compiler and un-check “Enable Strict type checking.”  This will allow the file to compile. 

However, when you run the TestApp you will see an exception thrown, not by Derek’s code like we’d hope but by the player, “TypeError: Error #1006: find_by_name is not a function.”

Tweak the Syntax

Just to keep things on the up and up I want you to go back and change that project property back ( Project->Properties then Flex Compiler and check “Enable Strict type checking ).  Then we can tweak the syntax of the TestApp.mxml line 8( blog = Blog.find_by_name… ) to be:

blog = Blog["find_by_name"]("Some Text Here.");

We still get a type error from the player, “TypeError: Error #1006: value is not a function.” but at least our syntax compiles cleanly.

Why doesn’t this work

To answer this question you might first want to go read “Object-oriented programming in ActionScript Advanced Topics” but to summarize, the “callProperty” method Derek overrode only works on instances of the class not on the “prototype” of the class which is where the static methods live.  So some how we need to access the prototype before execution.  Sadly, there is no proxy method like “callProperty” for the class’s prototype, so we have to go in a more ghetto direction.

staticInitializer

The direction to move in is to use a static initializer in the Blog class to kick off building the static methods we need.  I will jump straight in the flow of the working solution.

Blog v0.2

The only thing we’ve now added to Blog.as is a call to staticInitializer passing in the prototype.constructor of our current class.  ( To understand what that means, check the OOP in AS article mentioned previously ).  This will allow us to insert some calls before anything in this object is ever called.  Think of methods like this as constructors for the Class object, not an instance of the class, but of the definition of the class — remember everything is an object.  This method is actually defined in the base class ActiveRecord.as:

ActiveRecord v0.2

So you can see a few things have been added, line 13, is just a list of methods we want to add to the object, you could generated these from anything you want(hint hint).  The definition for staticInitializer in line 19 is where the real stuff starts to happen.  In this simple example we will loop across the functions we want to add then create a new anonymous function that remaps a bunch of parameters to our function called endPoint, which really handles the function call.  This allows us to easily do anything we want based on, the class name, method name and argument list.

Tweak the Syntax, Again

If you want to make it look like a normal method call again, you can change that compiler flag back to disable strict type checking and then call your new dynamic static functions like normal.

There maybe more posts in this area, extending this concept out to create some very useful Rails-ish Actionscript libraries.

Now, onto why I’m posting today, along the way I found some annoying things about how FlexBuilder played with the SDK.  For instance, the .flexLibProperties file that is hidden in your FB project, is not the right format to be taken in as a parameter to “compc” ( the library compiler, which seems to require a list of class names to include ), so I wrote a quick Python script to convert that file into a config file that is readable by compc.  Here is how to include it in your Ant script:

<target name="setupClassList">
    <exec executable="python" failonerror="yes">
        <arg line="${helperDir}/classFileConverter.py ${lib_root_dir}/.flexLibProperties classes.xml"/>
    </exec>
</target>


 

It takes in two parameters so you can manipulate the output location of the new file.
Another odd part is that the application descriptor for an AIR project doesn’t get correctly populated.  FB itself fills in the <content> tag for you when it goes to compile.  If you look in your source directory the application descriptor has this string, “[This value will be overwritten by Flex Builder in the output app.xml]” instead of the name of the SWF.  One more little python script:

<exec executable="python" failonerror="yes">
    <arg line="${helperDir}/appDescrFix.py ../bin-debug/${app_descriptor}"/>
</exec>

Of course, I am going to give you the scripts!  Here are the links:
.flexLibProperties Converter
Application Descriptor Fixer

If someone knows a much easier way to do this just using the command line tools and/or Ant, I’d love to hear it!