Translation of "PureMVC Implementation Idioms and Best Practices"Another translations: into French, into Japanese, into Russian. | Participants
|
- Statistics
- Participants
- Translate into English
- Translation result
- 0% translated in draft.
If you do not want to register an account, you can sign in with OpenID.
PureMVC Implementation Idioms and Best Practices | ||
Inspiration | ||
PureMVC is a pattern-based framework originally driven by the currently relevant need to design high-performance RIA clients. It has now been ported to other languages and platforms including server environments. This document focuses on the client-side. | PureMVC is a pattern-based framework originally driven by the currently relevant need to design high-performance RIA clients. It has now been ported to other languages and platforms including server environments. This document focuses on the client-side. | |
While the interpretation and implementations are specific to each platform supported by PureMVC, the patterns employed are well defined in the infamous ‘Gang of Four’ book: Design Patterns: Elements of Reusable Object-Oriented Software | ||
(ISBN 0-201-63361-2) | ||
Highly recommended. | ||
PureMVC Gestalt | ||
The PureMVC framework has a very narrow goal. That is to help you separate your application’s coding interests into three discrete tiers; Model, View and Controller. | ||
This separation of interests, and the tightness and direction of the couplings used to make them work together is of paramount importance in the building of scalable and maintainable applications. | ||
In this implementation of the classic MVC Design meta-pattern, these three tiers of the application are governed by three Singletons (a class where only one instance may be created) called simply Model, View and Controller. Together, they are referred to as the ‘Core actors’. | ||
A fourth Singleton, the Façade simplifies development by providing a single interface for communication with the Core actors. | ||
Model & Proxies | ||
The Model simply caches named references to Proxies. Proxy code manipulates the data model, communicating with remote services if need be to persist or retrieve it. | ||
This results in portable Model tier code. | ||
View & Mediators | ||
The View primarily caches named references to Mediators. Mediator code stewards View Components, adding event listeners, sending and receiving notifications to and from the rest of the system on their behalf and directly manipulating their state. | ||
This separates the View definition from the logic that controls it. | ||
PureMVC Gestalt | ||
Controller & Commands | ||
The Controller maintains named mappings to Command classes, which are stateless, and only created when needed. |
