Pretty amazing blog post by Jonathan Rosenberg, Senior Vice President, Product Management of Google. Some might argue Google isn't open about search algorythms etc. But I think they have proved that the opposite business model of the traditional hook, line and sinker is worth a consider.

Recently I was looking into Continuous Integration and as you do I started thinking of all the automation I'd like to integrate in an ideal world. One of them was running accessibility tests. As this is a bit of an unknown subject to me, I thought the ideal time arose to learn more on this topic and not to just accept the vanilla response that Flash is accessible.

Maybe you've guessed it but keeping with my black theme I've utilised my spare time to design a new set of Eclipse icons and splash screen. What I haven't had time for was writing some script to install these on different OS' but my guess is you will figure it out.

Initially I wanted to do a complete write-up on what it would take to move your entire Flash operation away from Windows. How much fun that would've been. Instead I opted for a more mashed-up approach on ethical philosophies and how they relate to the workflow of building RIA's and Flash websites mmkay.

Just read through the overview and the new FlexUnit4 alpha is looking pretty good. Using meta tags to create Tests and Suites and the addition of user defined tags, makes me think that I have to start including this in my own project workflow. I wonder how many Actionscripters actually use Unit tests. I'm sure there are a lot of Enterprise Flex developers but any pure Actionscripter takers?

[Update: Updated the link to FlexUnit]

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.