This guide explains how to set up a Flash and Flex development environment with Eclipse, FDT, Flash Builder and a couple of other editors that you want for ActionScript coding and Flash development with style! This guide is based on Windows because that’s what I’m using but I’m sure you Mac and Linux guys can figure out the parts that differ on your OS! Let’s get started …

>> Continue reading "Setting up the Ultimate Flash Development Environment"

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.

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!

You can click the image to see a full screenshot of the tool. In case you’re wondering … no, I’m not working on a Flash version of Uridium 2 (would be an idea though). The tileset is only for testing purposes.

Then there is the highly anticipated Flex 2 book which is due for the 1. quarter next year and so it still takes a while until then. Another book I’m looking forward to is Advanced ActionScript 3 with Design Patterns, also by Joey Lott, especially because I still haven’t fully grasped patterns. Maybe this will help.

You can generate names for planets and for characters, there are some parameters that can be chosen from before pressing the Generate button. After that it will spit out a list of more or less useful names (some of them sound very exotic). Interesting names can then be dragged and dropped onto the right side list. All names in this list are stored in local shared object on the users computer until the Clear button is pressed. The Switch button displays the saved names in a text area from where the names can be copied to the clipboard. (Small update: Works now with latest Flash Player v9).

(Please open the article to view the Flash media.)

© 2006 H1DD3N.R350URC3. | Permalink | 4 comments | Tags: AS3, Flash, Flex, Game Design, Lab, NameGen, Star Wars, SWF, Tools | Add to del.icio.us]]> http://blog.hexagonstar.com/starwars_name_generator/feed/ 4 http://blog.hexagonstar.com/the_joys_of_public_beta/ http://blog.hexagonstar.com/the_joys_of_public_beta/#comments Wed, 10 May 2006 06:38:42 +0000 sascha http://blog.hexagonstar.com/the-joys-of-public-beta/ Flex 2 public beta3 was just released and already all formerly written Flex2 beta2 apps started to fail working in the newest Flash Player! Seems like Adobe is making critical changes to the framework faster than we can change our pants!
This somehow spoils it for me to write more stuff with Flex until the very final release is published because I’m pretty sure it will fail working in a soon cooming beta4!
Yes, there’s a big and fat beta glued on it so it’s clear that changes are ahead and former stuff might fail but it’s all public and it’s obvious that Adobe isn’t only making it a public beta for testing but also for propaganda! My written SWNameGenerator doesn’t work anymore, giving me a nicely red flooded Eclipse editor full of errors!