This is the second part of a series of posts detailing the migration of a Flex 3 AIR 2.0 application to Flex 4. In this post we’ll start converting old MX components to the new Spark components architecture. Converting Flex 3 Microphone application to Flex 4Original Source Files Flex 4 files as Flash Builder 4 project (.fxp) Part 1 Part 2 (this post) Part 3High Level – The Before and After of this Post in Code Before just talking...

For AIR 2.0 release on labs.adobe.com I created a Microphone Example application showcasing the new feature that allows access to raw microphone data in Flash Player 10.1 and AIR 2.0. This application is a custom chrome AIR application that uses a lot of CSS and embedding of assets, both fonts and images. I figured it would be a good use case for migrating from Flex 3 mx components to Flex 4′s Spark components. As there is a bit to cover...

I needed to draw some dashed lines and polylines for something I was working on. I was already using Degrafa and wanted to create the dashed lines by extending Degrafa. It was actually easier then I thought it would be. You can see the finished result here and the view source code is enabled through right clicking. The two new classes DashedLine and DashedPolyline extend Line and Polyline and added two new properties “dash” and...

There was a small change in Flex 3 that causes the RemoteObjectAMF0 class to not compile in Flex 3 apps. I have updated the class and the swc. The updated RemoteObjectAMF0 code can be found in the renaun_com_RemoteObjectAMF0_flex3.swc in the zip file at – http://renaun.com/flex2/RemoteObjectAMF0/renaun_com_RemoteObjectAMF0.zip NOTE: updated again to add a line to delete references to the responders after it is passed...