Chances are you've heard of the term or read some tutorials on how to use these diagrams to help with documenting your thought process when building a slick Flash project. I basically only wanted to share a little gem I've recently discovered but ended up writing propaganda. I digress.
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.
After a great Max in Milano, I was inspired to start playing around with Pixel Bender. Granted, I wasn't going to create a raytracer and for someone who still struggles to understand the ColorMatrixFilter I thought the outcome of this tinker is pretty useful.
