May
06

2

Cairngorm - 1 Data Binding

In my introduction to Cairngorm I covered a list of features that I have found very handy. One of the most useful, and easiest to understand, is Cairngorm’s ability to maintain application state. Before adopting Cairngorm, I found myself passing data all over my applications. Not only was it hard to track down bugs, it made the application tightly bound. Cairngorm uses a singleton to keep application state. This is achieved though an empty interface called ModelLocator. Empty Interface? Yes, that’s right, it’s an empty interface that isn’t referenced anywhere. At first I was puzzled by this, and left it out of my code. After several projects, I decided to add the ModelLocator reference back into my classes. Although it is useless and not needed, it does let you know right away that the class is a singleton.

Full article...

May
05

Cairngorm - First Steps

What is Cairngorm and is it for me?

Actionscript seems to be a brave new world for developers; the rules are loose, the compiler is forgiving and there are many ways to get the job done. From application to application I have seen perfect object-oriented architectures, overly complex ego coding, and sloppy spaghetti code. When you are sitting down to design an application, consider existing code and design patterns. Why reinvent the wheel? The Flex architecture makes many patterns available to you and third-party frameworks (micro-architectures) are available for free.

Full article...

Page 2 of 2 pages  <  1 2