Looks like my XSD4MXML tutorial post was like so 1999 'cause the boys over at FDT delivered the beta release 3.2 with MXML support the 13th of March already. I can't keep up these days. What are you waiting for? Get it now! 

For those of you who want to get some MXML support in FDT I thought I'd share this little tutorial. I can't take credit for this as it was the guys from FDT who pointed this out at recent visit to LFPUG and Adobe MAX Milano way back in 2008. Lets hope we get FDT to support MXML natively so this isn't required but until then here goes. A small caveat, this will probably not work in Flex 4 as I remember them removing the mx namespace for the framework.

I'm currently working on a project of which the source will be distributed across the globe. So I want my code to be nice and tidy and send over some HTML docs to show off. Only problem is it's a Flex project and I've been out of touch with Flex for a while. As I don't use Flex Builder, getting ASDoc to work ended up on the things-I-will-sort-out-later-pile. For this project however, it was a requirement. So no easy way out.

Omniture is one of the leading analytic vendors out there. Chances are that if you're an Actionscripter you will come across implementing Omniture tracking on one of your projects. I briefly overviewed various tracking in a previous post but thought it might be useful to cover this vendor in-depth. Usually this level of tracking implementation are done on medium to larger flash projects or where the project is part of an online campaign. Smaller sites often don't require this level of tracking and a straight forward implementation of Google Analytics should suffice.

Omniture like many others use Javascript to make requests to a server, passing key-value pairs, to record user activity. Omniture also has a Flash component called ActionSource for more advanced tracking. This post will focus on the ActionSource component and the Omniture setup in general. If you require more information on the Javascript implementation, please read my previous post.

This article should provide you with all the ammo you need when using the Embed meta tag. It is a vital part of AS3 and should greatly enhance the structure of your projects. Hopefully this article will show the benefits of structuring your projects in this way.

Error: No class registered for interface 'mx.resources::IResourceManager'. If you have experienced this before, you are in for a bumpy ride. There are loads of these errors floating about when using the flex sdk to compile your project with. The reasons are vast and different but basically boils down to dependencies. Classes within the flex framework depend on a heap of other classes, that is why it is known as an Application framework.

This is something we all experience on a daily basis, we want to use some piece of code written for a previous project, and quite often we find ourselves spending way more time to make the code standalone that we would have like to. Very similarly, I want to use the RPC package for various reasons but without using the whole Flex Application framework.

So where does ResourceManager fit in and why is there no class registered for interface IResourceManager?

Andre Michelle is making some noise. After playing with PopForge, I have nothing but total amazement of what this guy does, there is no reason not to support him in his quest to get Adobe to fix some serious Sound API problems.

I filed this bug this morning and thought it deserves a post as it took me quite a while to figure out how to do this. Now I know you won't necessarily be migrating for Flex 2 SDK to Flex 3 but you might and if you do please read on.

Here is the official bug. In a nutshell the problem is when you compile a project using the FDT Application features for AS3 projects with the Flex 2 SDK. I then migrated to the Flex 3 Beta SDK and the project was still compiling using the Flex 2 SDK. WTF?

This post is aimed at beginner Actionscripters. It covers all the basics of setting up Eclipse and FDT environment to develop some kick-ass websites in a more structured Object Orientated approach. From managing workspaces to connecting with repositories, this document should be all-inclusive for any new Actionscripter who wants to start doing some serious Flash projects. If I missed something please feel free to comment or send it to me so I can update this post.

You can download this post in PDF format here »

The concept is simple. Improve workflow between designers and developers. Ever since I can remember, everyone always talked about improving this relationship. Get designers to do more towards project setup than they normally would be accustomed to, without having them type a single line of code. The reasoning behind this is simple because it is not always possible to technically implement the design. The only alternative is to manage expectations or at least that was until now.

I stumbled upon this gem in the Flex API about the intensity of the setStyle() method on processing. I only recently had the need to use it and was quite shocked at how slow this actually was. Granted I used it on a Datagrid which is probably not the best idea but I'm a bit of a if-it's there-then-use-it-kinda-guy.

Joan Lafferty blogged about the upcoming changes in Moxie for setting component and sub-component styles. Very insightful article. It immediately made me ask the question. How does this impact the setStyle() method. Presumably the "StyleProxy" should alleviate this problem as you have more control over what style is set to what component, regardless of the hieracrhy.

See the warning in the Flex api here »

I was struggling with this for a bit. But luckily there is a quick work around. It seems the scope is lost for the event listener when using flash.system.File browseForOpen(), i.e. your handler will never know when a file is selected. The solution is to move the variable outside of the function - create an instance variable of File.

Read this thread for more info:
http://www.adobe.com/cfusion/webforums/forum/messageview.cfm?catid=641&threadid=1275