In this chapter you were introduced to the Cairngorm framework, including its history, guiding principles, major components, application logic flow, and organization.
Cairngorm promotes the separation of code by roles/responsibilities and facilitates team development, in that different parts of the application can be worked on in parallel.
As I mentioned in the history section, Cairngorm borrows many of its solutions from the J2EE world. If you are coming from a computer programming background or have previously worked with Java or some other object-oriented language, many of these solutions may be familiar to you.
If you are coming from more of an ActionScript development background, they may be less familiar, since ActionScript is a less rigid language than Java and standards and practices still vary greatly in the world of ActionScript development.
Regardless of your current experience, the beginning chapters of this book discuss the underlying principles that inform Cairngorm and look in more detail at the major components defined in this chapter.
After examining these components, you will complete a brief sample application so that you can see examples of how these components work together to form application features.
Once you have completed the sample application, criticism and best practices related to Cairngorm will be discussed, as these will be more informative after you have worked with the framework.