Flex 4 cairngorm 3 Parsley 2.2

[Galimberti]

My question now is whether Cairngorm is a "good" framework or is at least useful. Being essentially a conglomeration of Best Practices, Cairngorm is very low binding, and thus easy to use. It provides the "subsistence" in VMC without imposing a heavy framework that would require a long learning for Flex developers. Can anybody have any idea about Flex 4 cairngorm 3 Parsley 2.2. Thanks.

[MindSpace]

Before even use or even look at Cairngorm, it is important to consider your application properly. This is why the first chapter of the tutorial is devoted to Cairngorm VO (Value Objects), which may seem like the basis for a J2EE programmer, since a VO is neither more nor less than a DTO. This is a typed object that represents a entitée your application logic.

[Zecho]

The use of the binding on which designers insist Cairngorn. The binding in practice that ensures the subject book will be updated continuously regardless of the changes that are performed with the interface. In practice the VO actually serve as an interface between the ski data from the server (and / or to be stored) and the views of Flex. And the binding provides the binder.

[opaper]

Cairngorm provides yet ServiceLocator who is also a singleton. It brings together all the remote access services (Web Services, REST, and others if we use the FDS) and provide a unique method of access. I used a program to test existing and CPP have "passed" in the Cairngorm: we have a DataGrid, a test button that displays a string that it returns the remote POJO, and a button to fill that through this referred to it by another method POJO, fills the DataGrid.

[Reegan]

There are ways to improve the design and make it even more Cairngorm-compliant, using Delegates. The idea is that a Delegate is responsible for access to remote data and the Command made only treatment. One can also imagine that the same is called by several Delegate Commands. It can also be functional or other groupings.

[Makayla-alex]

The binding on which designers insist Cairngorn. The binding in practice that ensures the subject book will be updated continuously regardless of the changes that are performed with the interface. In practice the VO actually serve as an interface between the ski data from the server (and / or to be stored) and the views of Flex. And the binding provides the binder.