Model Locator : Stores all of your application’s Value Objects (data) and shared variables, in one place
View : One or more Flex components (button, panel, combo box, Tile, etc) bundled together as a named unit, bound to data in the Model Locator, and generating custom Cairngorm Events based on user interaction (clicks, rollovers, drag-n-drop etc.)
Front Controller : Receives Cairngorm Events and maps them to Cairngorm Commands.
Command : Handles business logic, calls Cairngorm Delegates and/or other Commands, and updates the Value Objects and variables stored in the Model Locator
Delegate : Created by a Command, they instantiate remote procedure calls (HTTP, Web Services, etc) and hand the results back to that Command.
Service : Defines the remote procedure calls (HTTP, Web Services, etc) to connect to remote data stores.
Mate Framework Mate framework it is a tag-based, event-driven Flex framework. Benefits Highly decoupled Your classes do not extend from Mate Business logic is independent of framework Can be tested & reused Business logic decoupled from events Business logic decoupled from services Events are normal Flash events Can be reused
Basic steps Typically, the basic steps to create a Mate project are: 1. Add the compiled framework code to your project (Mate.swc). 2. Create a file that will be the EventMap . 3. Include the event map in your main Application file. 4. Create a custom event. 5. Somewhere, dispatch that event. 6. Add EventHandlers in your event map that listen for the event type you dispatched. 7. Execute some actions inside the EventHandlers block (ie: call the server, store data, etc). 8. Repeat 4-7 for every event you need.
Summary The MVC pattern provides a clear framework for design. The separation of responsibilities among the model, view and controller elements allows easy substitution of elements without disruptions to the overall application. This lets us easily expand applications based on the MVC pattern to meet changing requirements.