With MAX right around the corner, you would expect some build up. For example, Cairngorm 3. Yes, kids, it’s true! A transformation is coming, which will make Cairngorm more than just a micro-architecture. Instead, Cairngorm is broadening its scope to become a collection of tools, practices, and libraries, all of which form a foundation for use in Flex development. At the core of it, Cairngorm still represents a layered architecture, separation of concerns, and test driven development. If it suits your needs, the original Cairngorm libraries are included, with many enhancements. On top of that, a wealth of additional information is added. This content is gleaned from the expertise of Adobe Professional Services and the Cairngorm Committee. This will allow the wider community to share the knowledge that we in Adobe Professional Services have acquired while developing large scale Flex applications. The additional components and recommendations expand beyond a single architecture, and will suit many of the frameworks now being used. This will broaden Cairngorm’s scope, making it a useful tool on any size project.
As to what ‘coming soon’ means, I’ll have to leave that up to your imagination. But when it does become officially available, be sure to check it out!
So, you need a spell checker? Finding the current options are either a bit limited, or not free? Adobe has just launched Squiggly, a spellchecker library based on an open source algorithm and dictionaries, as a project on Labs. With Squiggly, you can add ‘check as you type’ spelling to your AIR or ActionScript application with easy to follow examples. It’s a ‘technology preview’ at this point, and only targeted at English for now, but still worth checking out.
Read the official Labs blog entry, or check out the online demo.
A few of the team in Adobe Professional Services have been working on a port of PMD to work with ActionScript.
From the overview:
FlexPMD is a tool that helps to improve code quality by auditing any AS3/Flex source directory and detecting common bad practices, such as:
- Unused code (functions, variables, constants, etc.)
- Inefficient code (misuse of dynamic filters, heavy constructors, etc.)
- Over-complex code (nested loops, too many conditionals, etc.)
- Over-long code (classes, methods, etc.)
- Incorrect use of the Flex component lifecycle (commitProperties, etc.)
A report is produced describing the violations of a given rule set. FlexPMD includes a rule set that is broad ranging and continually growing.
We have been using this on my current project, and it’s a great tool. Especially handy is the ability to edit or create the rule set. This also integrates well with continuous integration tools, providing updated reports ever time the build scripts run.
Check out on Confluence, the Adobe Open Source website (you may need to log into Adobe to view the link):