An update?

2008-06-13T13:28:00.001-07:00

Yep. An update. Something I whipped up in Flex. Enjoy.

Heh

2008-05-15T08:58:00.000-07:00

So obviously I've abandoned some ideas I've had lately in lieu of sitting around and doing nothing for a while.

Ever been having a conversation with someone, and you find you're having two different conversations at once? It would look confusing to the outside world I imagine.

Some ideas

2008-04-13T02:28:00.001-07:00

So I've got a little bit of free time today, and I've already slept as much as I can and it's only 10am.

I've decided to see if I can remake the OSX Dock in Flex, which should be interesting. When I've produced something meaningful I'll post it here with the source for other people to learn from :)

I'll have you for breakfast!

2008-04-10T08:15:00.001-07:00

Coded entirely in Flex 3

Smoothing
Deblocking
Aspect Ratio Preservation
Post Roller
Special Effects
Full Screen
Volume Control
Fully Skinnable

I win

What you're ACTUALLY supposed to do instead of eval()

2008-04-10T07:44:00.001-07:00

I recently came across an article on the intertubes, a helpful individual with good intentions offered the following information (here's the original post):

ActionScript 2.0 had eval(), which allowed you to execute arbitrary ActionScript. ActionScript 3.0 doesn’t have it. I’m accustomed to being able to execute arbitrary JavaScript generated at runtime. It’s a pretty powerful feature, and it’s hard to give it up. I think I understand the rationale for getting rid of it (mostly for performance), but what to do instead?

Well, it turns out that one thing you can do that is really better in some ways is to call a method whose name is generated as a string at runtime. This gets you the same sort of dynamic execution, but it’s a lot more predictable and less chaotic.

To do this, you need to include the keyword “dynamic” as part of your class declaration, e.g., public dynamic class Foo. Then to make the call, just say:
var functionName:String = "foo" + bar;
if (this.hasOwnProperty(functionName))
this[functionName]();

Now this is all well and good friends, but not entirely accurate. As happens, things get updated and things often change.

I saw this code and instantly thought: "If Flex has the functions as part of the this[] array, then it's most likely that it stored all the other variables and objects as well."

Well folks, I was right. If you're trying to access Controls, Objects, Variable or Functions, They are all accessable through this. Like so:

playlist = XML(event.target.data);
videosXML = playlist.video;

for (var xml:String in videosXML) {
var url:String = videosXML[xml].@url;
var img:String = videosXML[xml].@img;
var txt:String = videosXML[xml].@txt;

this['plug'+xml+'url'] = url;
this['t_plug'+xml+'img'] = img;
this['l_plug'+xml] = txt.length > 14 ? txt.substr(0,12)+'...' : txt;
}

Most interesting ;)

Haxing Flex

An update?

Heh

Some ideas

I'll have you for breakfast!

What you're ACTUALLY supposed to do instead of eval()