How about adding EasyMVC?

@Andy

EasyMVC has been added, how could I forget Simeon.

For those who are interested in the effectiveness of different frameworks you can see this article from my colleague Vladimir Tsvetkov:

http://npacemo.com/wordpress/2008/10/03/introduction-to-flex-applications-architecture-part-3-the-gugga-approach/

He suggest an approach that is proven from our practice to be very effective.

I found Cairngorm to be overly complex and in a lot of ways, a square wheel.

For example, why do I need to raise an event that gets handled by a front controller and routed to a command? Why not just invoke the command directly? The front controller pattern is trying to claim that keeping all of my commands in one place is agile. Actually, by removing the command's invocation from its natural context, I found myself spending a huge amount of time trying to remember where the source code related to the event was. After I finally found the correct code, I was trying to remember what I wanted to do with it. Overkill.

I also disagree with using the command to move data between delegates and the model. The object model should represent the semantics of the application, and encapsulate calls to persistent data. Yes, the delegates should be decoupled to allow for different data sources. But, from the command object's point of view, the requirement of invoking both the delegate an the model independently is poor encapsulation.

Lastly, the model locator pattern is an "atrocity." See the link below, which I totally agree with:

http://blog.iconara.net/2008/04/13/architectural-atrocities-part-x-cairngorms-model-locator-pattern/

Can you add Ruboss too? It's a Flex framework which makes it easy to talk to RESTful CRUD web apps (currently Rails and Merb).

We use an in-house framework (which I'd like to get OSS some time). None of the other available frameworks feel "right" to me.

Tom Bray's EasyMVC - simplified version using the same approaches as Cairngorm with no swc files required.

As johans said, We use Tom Bray's EasyMVC, which is very simple, but uses most of the concepts used by Cairngorm. There are lot of interesting features in the available frameworks, and we kind of mixed everything together and made an in-house framework... which is working nice - faster development, and multiple developers on the same project, no confusion on how to deal with events and commands etc...

we use a framework developed inhouse called GEMVC - (Good Enough) found here - http://gemvc.riaforge.org/

it uses many of the cairngorm conventions so anyone familiar with it could adopt it easily.

There is a lot of open source frameworks in Flex but just a few open source application, so having source code sample is not always easy !

Anyway, we have used PureMVC for 1 year and we are happy with it. If you want a real example of PureMVC application, you can have a look to Igenko source code.

As this seems to be a good place to list existing Flex frameworks, GraniteDS includes a simple component-based framework for Flex 3 which is very similar to JBoss Seam and makes use of Flex 3 custom annotations.
It is designed to avoid the whole lot of boilerplate code implied by Cairngorm and other similar MVC based frameworks.

I had a hard time saling the idea of using Cairngorm or Universal Mind Cairngorm extensions in my organization. The main show stopper was the use cairngorm events instead of just plain flash events. The use of Cairngorm events forces all the modules to use Cairngorm. I did some research and learned about Mate. Mate uses flash events and therefore the framework is not invasive as Cairngorm.

I used cairngorm for a while, but ended up writing my own Dependency Injection Framework...It's a bit more flexible. I just released it on Google Code. I call it "Mainline." I'll be posting some examples and advanced usage tips over on my site over the next few days.

Mainline Framework