Having learned how to program mainly with Java and VB.Net, the approach I wanted to take was to have two threads running in my flash movie : one that fetches and treats the XML data, the second that handles events, collisions and the movement of the MovieClips. However, to put it bluntly, there is no such thing as multi-treading in Flash 9.

The approach I chose to solve this problem was to generate calls to key function of my main class using the setInterval function. Of course, on a much larger scale, one would probably notice a lag when using an interval technique compared to real simultaneous treading. However, with the usual Flash applications this kind of performance goes rather unnoticed.

Here’s an example similar to what I am doing:

class Feed {
    public function Feed():Void {
        setInterval(this.refreshFeedData, 500);
        setInterval(this.moveFeedMovieClips, 500);
    }
    public function refreshFeedData():Void {
        // load the xml
    }
    public function moveFeedMovieClips():Void {
        // run through my MovieClip objects
    }
}

By keeping a frequent and similar intervals (in this example 0.5 seconds), you can somewhat mimic the threading effect. Note that you can lose the reference to the class using “this.” in the function being called by setInterval . You can go around it by supplying a reference to the current class in the call :

setInterval(this.moveFeedMovieClips, 500, this);

A problem came up however. I needed to loop through a specified local folder recursively in order to load the *.gifs, *.pngs and whatnot in the local file structure. Flash 8 has added file management support with the FileReference class. It’s neat browse() function mimics HTML’s file input to pop the file browsing dialog. There were two problems with this class:

• I couldn’t select a directory;
• I couldn’t select multiple files.

Screwed aren’t we? I’ve also learned you could browse through local files using an ActiveX valid only for IE which is completely useless. All other solutions involve fetching the files using server-side scripting like PHP or ASP which no one have installed on their desktop anyway (if you do have one of these installed, then you are official a nerd).

So, desperate but not without motivation, I’ve downloaded Mac’s software development package in hopes of building it on that platform. We’ll see how it goes.

For about 2 years now, I wanted to make a full blown flash game. I’ve done a few unfinished sketches, have tried to build an adventure game engine, then I tried doing an RPG engine, then followed a simulation game, and then I tried making an RPG again. Hell, I even tried to make a hockey game.

Do I even need to say making a real flash game it’s hard as hell?

That’s without mentioning the common cliché of Real Life catching up and forcing me to put my projects on the ice for a while. Also, just like any project you do without thinking thoroughly before beginning, after a while you start noticing how the programming sucks, how the same thing could be done in a much simpler way and all that depressing crap.

Well! Now I feel like going at it again. Though I don’t know how much time it’ll take me, I have decided on continuing Rise of the Espers (read: start it over again). This RPG is meant to be similar than those of the SNES and should be a mix between Final Fantasy 3 and Secret Of Mana. We’ll see how that will go!

Of course, you can’t quite tackle a task like that without help. Even if I’ll probably end up making everything myself, I will need the help of those with more “mathematical” minds that mine. It was by asking Evilmax help on how I could generate an isometric map dynamically that he came up with the idea of having me publish the game’s progress. Without further ado, here’s the first post in a long series in the Rise Of The Espers: The Making of.

“Let there be light”

Here is a screenshot of the game’s architecture at the moment. The Game.as file is where I will be handling the game’s interface (new game menu, options menu, save, etc). The Map.as class will generate the map using data from an XML file and by creating a Tile.as object per each texture tile.

Utils.as is a file I’ve been using for a while in many of my projects. I store usefull static functions in there like the event handlers.

game.fla is an empty file with only a call to the Game.as’ constructor in the actions layer of the first frame.

The map itself is created from an xml file that contains arrays of numbers which are each associated with a image in the game.fla texture pack. For performance issues, the texture images are likely to be pixel images and not drawn in Flash.

The game.fla file does more than it is supposed to be doing at the moment. As the project grows in maturity, game.fla will handle game menus, pauses, server connections and whatnot. To continue loading the maps, I will create another placeholder movie where only Map instances are created. This map movie loader will be loaded from game.fla using the loadMovie() command.

Extensive use of the Progress bar control warns of data transfers delays but is also used with each heavy loops, like the one that creates the tiles. While you don’t even see them when I start the game from my desktop, they will be much appreciated on the web. I also use the alert component to raise error messages.

And that’s where I stand at the moment, the movie loads a simple map of two textures dynamically. The next step will be to draw the main textures and build a quick interface in flash through which I will be able to save my arrays automatically, and not have to learn all the texture codes by heart.

class Utils {
// Desc		:	Usually, when you attach a function to an event, you can't pass
//			parameters, using this function instead of the Delegate class
//			will allow you to do the same thing but with unlimitted parameters
// 			Window: General Information.
// 			http://www.person13.com/articles/proxy/Proxy.htm
public static function delegateEvent(oTarget:Object, fFunction:Function):Function {
    // Create an array of the extra parameters passed to the method. Loop
    // through every element of the arguments array starting with index 2,
    // and add the element to the aParameters array.
    var aParameters:Array = new Array();
    for(var i:Number = 2; i < arguments.length; i++) {
        aParameters[i - 2] = arguments[i];
    }
    // Create a new function that will be the proxy function.
    var fProxy:Function = function():Void {
        var aActualParameters:Array = arguments.concat(aParameters);
        fFunction.apply(oTarget, aActualParameters);
    };
    return fProxy;
}

And you can call it like this:

private function someFunction():Void {
    this._xml.onLoad = Utils.delegateEvent(this, xml_onLoad, "GeneralInformation");
}

private function xml_onLoad(success:Boolean, nextStep:String):Void {
    if(success)
    // Get the contents of xml
    switch (nextStep) {
        case "GeneralInformation" :
            this.open_GeneralInformation(); break;
    //etc...
    }
}

This was a huge time savor and suits how I like to write code.

class Foo {
	public var _someProperty:String
	public function Foo() {
		// Lets skip how I actually make the button,
		// but I usually use .attach() and I make
		// exportable the object in the Library. I
		// think I should use createClassComponent however.
		var but:MovieClip = new MovieClip();
		but.onPress = function () {
		_root.MyFooObject._someProperty = “Clicked”;
		}
	}
}

To access my attribute, I must leave my class and follow the absolute, practically hard-coded, path to my value. It’s really not a good thing to do. Instead, I found you can use the Delegate class to forward events to a function inside the parent class. Like this:

class Foo {
	private var _someProperty:String
	public function Foo() {
		// Lets skip how I actually make the button here too.
		var but:MovieClip = new movieclip();
		but.onPress = mx.utils.Delegate.create(this, button_onClick);
	}
	private function button_onClick():Void {
		this._someProperty = “Clicked”;
	}
}

Where “this” means the class you are in (could be another one), and “button_onClick” is the name of the function you will be calling after the event is triggered.

There you go! It’s a lot more powerful, much more logical from a semantic point of view and it makes the code a lot clearer. Notice how I can protect my call properties now using the private attribute.

Speaking of being semantic, you always should call you call properties with “getters and setters” instead of calling it directly like I did in my example. It should look like this instead:

private var _someProperty:String
public function get someProperty():String { return this._someProperty;}
public function set someProperty(val:String):Void {
    // validation if needed; this._someProperty = val;
}

I decided on making this using Flash, just like Yahoo Maps have. From the start, the most important feature was how I had to permit a click event somewhere on the map and to center the map on these X and Y coordinates. At first, I approached the project by planning on incrementing a value to the _x and _y properties of the map MovieClip for some period of time to mimic movement until the map was re-centered, but I’ve had no success doing so.

That’s when I had a revelation. Once you start trying to build Object-Oriented applications in Flash, you tend to forget all the design tools built-in Flash. Why didn’t I call the Tween function from within ActionScript? And so I did.

Here’s the relatively simple function call to move a MovieClip object using the Tween class:

new mx.transitions.Tween(MovieClip, "_x", easeType, begin, end, speed of execution, time unit boolean);

You pass on a MovieClip, the property you wish to edit (in Flash, the properties all start with “_”), the effect you wish to use for the transition, the starting value (for the _x property, MovieClip ._x for instance), the end value (passing MovieClip ._x + 50 would create a motion tween that would move the MovieClip 50 pixels to the right from its original location), and the speed of execution which is either counted in seconds or in frames depending on the last Boolean parameter (true meaning seconds).

It’s really flexible and powerful. Passing in a different easing type will allow you to apply built-in elastic or bouncing effects to a MovieClip. Now all of the bouncing menus we see all over the Internet seem much simpler.

You can also pause, rewind and do other operations on the Tween process because it generates events as the animation plays.

It opens a lot of doors to OOP in Flash. You no longer need to bother with sketchy animations when forcing movement on your MovieClips from within a Class.

If you code in Flash and have never come across this function, I strongly suggest you read more on this undocumented function.

One of the components I’ve played with it the Window object. It’s simple to understand and it’s possible to create a Window on the fly using ActionScript only. Let me put some emphasis on that. Within a few lines, I was able to program my way into a graphic application. We can all agree that’s the goal behind the general direction Macromedia is taking and to a certain extent they are succeeding in doing so.

However, other components are much harder to instantiate or create/call straight from ActionScript. The documentation on Live Docs is also somewhat deficient. I’ve tried a gazillion times to have the XML connector work when created dynamically but couldn’t make it work yet. The media playback was a bit easier to build with dynamic values, but as I write this, the Mp3 player on The Music Tank still has trouble opening .mp3 files consistently.

What I hate about components is how I never know if it’s my fault if it’s not working. If it is (which is probably the case) there are two questions I can rarely find answers for:

• Am I supplying invalid values which failed validation once the control is speaking with my website? And
• Is the control not working because I instantiated its properties with wrong values?

I hope Flex will make it easier for graphic artists who are able to do real Object-Oriented programming. Right now, I feel pretty dumb having to use illogical code just to make up for Flash’s “almost-there” programming language.