In August last year we started looking at alternatives for the typical Cairngorm 2 approach, having used it on a number of large projects we didn’t really see it as a framework suited for the kind of applications we develop in Lab49. Some of the issues we were struggling with was the difficulties with integrating with modules, the amount of boiler plate code like events, commands, delegates, responders for every single thing you want to do, etc. Another common problem with Cairngorm 2, and other frameworks, is managing presentation models and the sharing of data without having a hierarchy of objects and passing it down from a parent view to all the children.

The search for a good IoC framework began, but there wasn’t a lot of frameworks out there that supported everything we wanted, but after some investigation the decision landed on Parsley. Parsley supports both Flex Modules and dependency injection, two of our main criteria. We have now successfully used it on a number of projects. If you are looking for an example of building a Parsley based Flex application, have a look at this blog post by Christophe Coenraets alternatively have a look the documentation, Parsley is comprehensively documented: Parsley Developer Manual

After a rather long introduction, here is the presentation: Scaling Flex for Enterprise Applications

The presentation is available on AdobeTV.

Who said Adobe Flex couldn’t be used for critical systems? If Adobe wants Flex to be seen as a serious framework in the enterprise, this is the kind of projects they need to show more of.

Over a series of posts I will cover some of the experiences gathered from this and other projects I have taken part in. There is usually more to a project then just choosing a framework like Cairngorm, PureMVC or one of the many IoC containers which are popping up everywhere.