After a lot of research it turns out that there seems to be no way in an AIR app to use the GPU mode that is otherwise supported by Flash embedded in HTML via wmodes parameter. In fact the docs state it’s not even supported by AIR …

… Flash Player 10 introduces two window modes, direct and GPU compositing, which you can enable through the publish settings in the Flash authoring tool. These modes are not supported in AIR …

While this is a definitive must for a hopefully soon appearing update there’s another issue with fullscreen modes … AIR doesn’t really feature any decent solution for fullscreen! You can have your app to be either in fullscreen OR in windowed mode but trying to be able to switch between both looks very ugly because the system chrome isn’t being disabled automatically when switching to fullscreen which results in that the window size will simply get maximized. So creating applications where you could let the user switch between fullscreen and windowed mode seems to be impossible at the moment with AIR 1.5.

I can understand that the Flash player on the web needs it’s security restrictions in this regard but AIR should definitely not be touched by this! I hope Adobe will improve this for a future update, AIR is a great platform for (complex) game development but these two issues are serious limitations to that!

“…and a component system which lets you easily package game functionality into reusable modules. The component system draws on nearly a decade of game development history…”

This looks very promising indeed and the component structure makes a lot of sense.

I’ve been working on the hexagonLib on and off but time is sparse currently and so it seems I would never get it into a decent release state. I Might as well see how the pb engine works out for me. Let’s see how this engine fits for my current role-playing game project!

So today I finally figured out how to install the plug-ins that I really need and nothing else (well … almost nothing else). The following guide describes how you can set up your own custom Eclipse tailored for Flash/Flex development which features FDT plus Subclipse, a HTML, CSS, JavaScript and XML Editor and then some. The CSS Editor becomes especially useful for Flex Stylesheets.

>> Continue reading "Setting up Eclipse for Flash Developers"

Besides that Alcon is now code-signed there is exactly one new feature in v3.1 which I called Key Tracer. You can toggle Key Tracing Mode from the Log menu. If you enable it you are able to press any keys and their key code (and if available character code) will be listed in Alcon’s output window which is a useful feature if you want to know the codes for some specific keys quickly.

More features where planned (and already started) like a Search function, Log Level Filtering and even a Calculator but these haven’t made it finished yet into v3 so most of them will come with version 4, which is – yet again – a complete re-write (I do loathe my source code that is over one year old ).

The newest version can as always be found here.

That’s right, I cannot buy the dev membership now because Apple’s site is obviously broken and thinks I’ve already bought the membership. An advice: DON’T leave the address fill-out page or empty your shopping cart! You will not have a chance later to come back and reach the page that puts the product into your cart.

But enough rant for today! I think I go and write some ActionScript … which is much more fun … and it’s FREE!

It seems that many newcomers to ActionScript still don’t understand the use of ‘this’ and that it’s only really necessary in rare cases, for example if a method parameter has the same name like it’s relative class property or in a few scope-related situations. It’s also good to have ‘this’ at hand if a dynamic property of a class needs to be accessed (this["foo"]) but other than that please do all a favor and throw out those unnecessary ‘this’! Ban it, lock it in your basement and don’t let it out unless there’s really a need for it!

override public function toString():String {
	return "[ClassName]";
}

… Sometimes adding properties to the returned String that give back information about the class, e.g.

override public function toString():String {
	return "[ImageClass, size=" + _size + "]";
}

But writing them rigid like that is a disadvantage when you decide later to refactor class names. Admittedly it’s also not a very elegant way so I got the idea to take the class name that is returned by getQualifiedClassName(). The only problem is that getQualifiedClassName not only provides the type name but also the whole package String of the class. Regular Expressions to the rescue! After twiddling around with them for a while (I’m by no means a RegExp expert) I got my toString method into the shape that I desired:

override public function toString():String {
	return "[" + getQualifiedClassName(this).match("[^:]*$")[0] + ", size=" + _size + "]";
}

This way it matches the String returned by getQualifiedClassName with the Regular Expression [^:]*$ which checks from the right end for an arbitrary text up to the first occurring colon, but without including the colon. Taking the first element of the Array returned by match() and you got what you need!

A nice way of using this is when writing abstract classes that contain the toString method and any subclass can use that toString method without the need to override it … that is of course unless you want ot add other output information.

I recommend to check out the Alcon Page for more details and of course the download link. Enjoy your debugging!

Then there’s the Options dialog with Trace options opened where you will be able to set font, colors etc. On the File Loggers Options you will be able to optionally enable up to two File Loggers that can be used for example to log the flashlog.txt to see output made by ActionScript’s own trace method.
There’s of course the new Object Inspector and a new Help panel for Quickstart Help and API Docs. Alcon 3 is being written 99% in ActionScript 3 using FDT (the 1% left being the Main.mxml that is necessary to compile a Flex application). It’s only a matter of a few days now until release, some bug fixing, finishing touches and a few more documentation to write and it will be out so please endure!

Some of the new features besides the already existing Trace Command and File Loggers are a Memory Consumption and Frames-Per-Second Monitor, a completely new and improved Object Inspector that is finally useful for Debugging, an Options dialog to comfortably configure Alcon, proper AS2 support and a couple of other minorities here and there.

The progress moves on quick enough that I dare to say that the release date is only a few weeks away from now so sit tight, it’ll be there in a heartbeat.

In game development randomness is often necessary for certain tasks, be it the random distribution of graphic tiles, a random factor in NPC AI or random stats in a roleplaying game. Especially for the latter purpose the static Dice class provides a set of methods to roll dice as it is common in a Role-playing game, to be exact four-, six-, eight-, ten-, twelve-, twenty-sided and percentile dice.

>> Continue reading "ActionScript3 Dice Class"

Makes me wonder why nobody else has yet written anything about this bug … when using any container component like for example a Panel or TitleWindow with a different borderStyle than the default, e.g. borderStyle: solid all your contents of that container reach into the the chrome of the Panel/Window/etc. pretty much messing up your layout. How could this escape the eyes of Adobe’s Flex devs? Here’s the thread at Adobe’s Flex forum. This is bad because it sort of prevents me from writing any Flex/AIR applications until this issue has been fixed, I’m using a custom theme for all my projects that use a solid borderStyle (similar to the one used in the Flex Style Explorer). The marvels of open beta software pushed by corporations for mere publicity purpose!

>> Continue reading "Animated Bitmap Class"

FDT 3.0 is pure coding comfort indeed! After using it you’ll agree that the Flex ActionScript editor looks like a poor excuse compared to FDT! There are all the features for ActionScript 3.0 that also were in FDT 1 and a lot of new stuff. Luxurious syntax coloring and semantic syntax highlighting, code templates,my number one favorite feature Mark Occurences, code formatter, quick fixes, Flash IDE and Flex compiler support, limited refactoring and more.

Now all I wish for is that FDT works flawlessly together with Flex/AIR projects but that will probably come at a later date since getting a stable release is more important now. It kind of feels awkward if you have to go back to the Flex AS editor once you used FDT!

>> Continue reading "Alcon"

>> Continue reading "ActionScript 3 MultiMap Class"

So what makes this game so addictive that people are coming back en masse? First and foremost it’s simple and straightforward. No long introduction, no necessity to read instructions, you get into the game quickly. Then there is the addiction factor … Maybe its just me but the reason why it is fun to play is because you try to make your defense perfect to stop the intruding enemies. Another factor is that you can shoot and destroy something. Sounds dumb? I know, but I can imagine that many people’s ‘hunting’ instinct is triggered by that. After all many popular games follow the same scheme. In fact you don’t even need to do the shooting as that is what your towers are doing for you. You just have to place them in a strategically good position and watch how well it works out. The author sure made a good choice by picking a Tower Defense game for this!

Now there are hundreds of other well proven addictive games out there. Make your choice and don’t forget to improve it by adding something that makes it even more fun to play! Meanwhile excuse me … I have to dig through my old games collection and do some searching …

>> Continue reading "Hexagon Framework Effects Demo"