I’m continuing evaluating of Flex frameworks and drawing exercises. After drawing Cairngorm and Mate, I’ve explored and drew the diagram of the PureMVC workflow. This diagram is not a replacement for the conceptual diagram included in the well written documentation of PureMVC, but it may give you a little better understanding of what’s going on under the hood. As usual, I’d appreciate any feedback or corrections that you may have.
Overall, PureMVC seems to be over-engineered. The learning curve is steep, too many tiers, dependencies, singletons. This frameworks has not been written specifically for Flex, but rather with a hope to be used in other languages as well. While I understand the desire of Cliff Hall to create a framework that’s works for everyone, this stopped him from taking advantage of what’s offered in Flex only.
I’m not a big fan of Cairngorm, but it’s a lot easier to learn than PureMVC, and at least it delivers on the promise to let people quickly get up to speed on large projects. Both frameworks don’t offer much other than separation of concerns, but Cairngorm would allow you to hire more junior programmers than PureMVC. If interested, I’ll be teaching an Intro to Cairngorm class in NYC on July 21.
Farata Systems is preparing a one day online hands-on workshop that will offer comparison of four Flex frameworks. If you don’t want to go through nitty-gritty details, consider attending Enterprise Flex Symposium in New Your City on August 19, where I’ll do a higher-level comparison of frameworks (readers of our blog can get 50% off the price by entering the discount code flex3halfprice).