Flash Camo (for short) is a graphics framework that allows AS 3 applications to be easily skinned from pngs, jpgs, or gifs. The framework is broken down into 3 core areas: Decals, the CSS Parser, and the CamoDisplay. These systems can be used individually or combined to fit your needs. When used together they form a powerful set of tools to help skin and style any Flash application. With Camo’s modular approach, you can use as little or as much of the framework as you want. The entire framework is under 35k.

Flash Camo is open source (under the MIT License), is compatible with FlashPlayer 9/10, Flex 3, and AIR. It can be built with the open source Flex SKD compiler or used in Flash CS 3/4 as a swc.

I have created a new Google Group to help answer questions about the framework and start open discussions on tips, tricks, and problems. Check it out here http://groups.google.com/group/flash-camouflage

Flash Tuts Plus Tutorial - Part 2 of my in depth tutorial walk through on how to use Flash Camo up on http://flash.tutsplus.com. Check out Part 2 here: http://flash.tutsplus.com/tutorials/workflow/intro-to-flash-camo-part-2

Flash Tuts Plus Tutorial - I just wrote an in depth tutorial walking through how to use Flash Camo that covers how I built http://jessefreeman.com. Check out Part 1 here: http://flash.tutsplus.com/tutorials/workflow/intro-to-flash-camo-part-1

Camo, v2.2.1 is now out and tagged. This includes minor bug fixes to the BoxModel. I also added an updated API Docs to the downloads along with a new SWC.

Camo, v2.2 is coming out very soon. There is an early tag of it if you want to try it out but I will be updating all of the documentation on the site to reflect the new changes. The updates found in Camo 2.2 focus on a rebuild of the DecalSheet system, removing unneeded classes from the framework and adding customization to the TypeHelperUtil.

Camo, v2.1 has just been released along with cleanups to the svn repo. If you had checked out the Camo from the trunk before please recheck out the entire trunk since it is up to date with 2.1. Also you should probably use tags of the Framework to help when future features are added to hopefully not break your code.