We’ll after studying Cairngorm and PureMVC for the past day or so I’ve decided to adopt PureMVC for my next Flex project.
Cairngorm had the scalability and robustness I was after but end the I went with the underdog. The best thing Cairngorm has going for it is the Adobe Machine and thus a large adoption pool. Kudos to Steve Webster and the rest of the Cairngorm authors, it is a well thought out and obviously scalable framework.
PureMVC seems cleaner to implement and addresses most of the issues you’ll find people gripping about with Cairngorm.
Anyways, time will tell, for now I’m jumping on the PureMVC bandwagon – thanks Cliff!!
I’m gearing up to start some medium scale enterprise projects and thought I’d look up this “Cairngorm” thing I heard talked about at the MAX conference in Chicago. The developers either loved or hated it, so I figured I should check it out. Basically Cairngorm is a design pattern framework for flex, an architect’s tool chest if you will. We’ll it appears that Cairngorm isn’t alone, here’s the lineup I ran across today…
Tom Bray’s EasyMVC
Simeon Bateman’s EasyMVC
(EasyMVC’s share the same name but are, in fact, different frameworks)
The latter two (EasyMVC’s) appear to be lighter weight frameworks, while Cairngorm and PureMVC both seem to be a bit more robust. PureMVC isn’t just for flex it currently supports or is in the process of been implemented in … Flex, Flash, AIR, FlashLite, .NET, Windows Mobile, Silverlight, J2ME, SE, EE, JavaFX, and well… PHP and ColdFusion.
I’m reading into all four frameworks to decide which, if any to further evaluate. I may adopt one for my upcoming projects or use them as spring boards to writing my own framework to help enforce the DP’s I’ve been studying as of late.