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"

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!

>> Continue reading "Understanding Interfaces and Polymorphism"

The question comes up why they don’t just ask the person who originally wrote the code! That could have many reasons but if a client comes back to me and asks me to fix something in a years old project then I’ll do it for a measly payment simply because I know my source code. It’s a total different thing to fix somebody’s code, especially if it’s pre-AS2.
I always feel uncomfortable rejecting jobs, even such ones so I would be interested how others handle this situation! Do you usually reject such jobs or do you accept them?

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23

package
{
	import com.hexagonstar.util.debug.Debug;
	import flash.utils.getTimer;
	import flash.display.Sprite;
 
	public class PerformanceTest extends Sprite
	{
		private var aVeryVeryLongVariableNameaVeryVeryLongVariableName:Number;
		private var num:Number;
 
		public function PerformanceTest()
		{
			var startTime:Number = getTimer();
			for (var i:int = 0; i < 4000000; i++)
			{
				aVeryVeryLongVariableNameaVeryVeryLongVariableName = (i * Math.random()) * 100;
			}
			var timeTaken:String = getTimer() - startTime + " ms";
			Debug.trace("timeTaken (long): " + timeTaken);
		}
	}
}

I’ve ran this code ten times with the 50 characters long variable name and then ten times with a 3 characters long one, both in their own SWF’s. The results ranged from 757ms to 820ms, more or less the same on both sides. The sum of the long variable version was 7924ms and the one of the three characters long one was 7903ms, not much of a difference.

The next test was similar but this time with a 50 characters long Method name and the other again with a 3 characters long one, the Methods returned a random Number for 4000000 times during this test. The results looked similar but the total sum of each test gave a 12044ms for the long name test and 15570ms for the short named one. A noticable difference of over 3 seconds. This might have been coincidence but I’ve ran the tests a couple more times and it turned out every time that the result were very close together. This is quite interesting because I was safely believing that short names would still have an advantage. It might be time to rethink this.

Found these today on my daily dose of Stumble Upon random links … Proggy Programming Fonts! Still coding with Courier? Maybe it’s time for a change?!

This brought up some moods of nostalgia remembering the ‘good old’ days of computing and playing 8bit games. I even found some old 5 1/4″ floppy disks with old tools and games and tried to code some assembler which is even fun in a special way compared to the today’s luxury of coding applications.

There’s also now – as you might already have found – a new category named downloads in which I will put various stuff to leech down from time to time.

Besides there are still some draft entries on hold and unfinished yet on the authoring side. I’m going to finish them when I think it’s time!