Learning Flash the Hard Way, from the Bottom Up

Whoever invented the Flash security model is an idiot that should be shunned from society. I’m too tired and frustrated to make the complete argument, but here are some tips:

If the web service you want to access is on HTTPS, you need to host the SWF on HTTPS too.
The most permissive crossdomain.xml I can figure [...]

Read Full Post »

So MXML is a slick tool for laying out UI components, but how do you interface the UI and the underlying application data structures? Meet the Repeater:

<mx:Application xmlns:mx=”http://www.adobe.com/2006/mxml”> <mx:Script> <![CDATA[ public var myArray:Array = [ "Hello", "World" ]; ]]> </mx:Script> <mx:Repeater id=”myRepeater” dataProvider=”{myArray}”> <mx:Button label=”{myRepeater.currentItem}”/> </mx:Repeater></mx:Application>

There’s a lot going on in that chunk of code, [...]

Read Full Post »

So I can’t help but notice every tag but mine starts with “mx:” and that “xmlns:mx=” is defined in the Application tag. My guess is this is mapping the “mx” namespace to definitions contained at “http://www.adobe.com/2006/mxml”.
Furthermore, because my tag doesn’t start with anything, that probably means it’s not in a namespace (or, rather, is in [...]

Read Full Post »

Ok, MXML is pretty sweet. We can make the panel tag in our HelloWorld application into a custom tag by simply creating a new file in the same directory as “HelloWorld.mxml” named “CustomPanel.mxml”:

<mx:Panel xmlns:mx=”http://www.adobe.com/2006/mxml” title=”Hello world!” width=”100%” height=”100%”/>

And let’s update “HelloWorld.mxml” to be: (Note the addition of the “xmlns=” attribute in the first [...]

Read Full Post »