|
matthewpotato
|
 |
« on: February 05, 2008, 12:38:52 » |
|
I'm creating a list of benefits of using PureMVC for people who haven't tried it and who aren't all that familiar with the MVC pattern. Are there any benefits I'm overlooking?
Notification system (publish/subscribe)
-------------------------------------
Components don’t need to know about one another’s existence in order to communicate. (Helps with modularization, code reuse.)
Communication can flow outside the containment hierarchy.
sendNotification(ApplicationFacade.LIST_LOAD_COMPLETE, showList);
Central data model
------------------
Having a model reduces redundant data fetching because value objects can be persisted within the model.
The model centralizes value objects that are accessed throughout the application.
Helps with separation of concerns
--------------------------------
The model manages value objects. Value objects are separate from the proxy class that manages them.
The view manages and displays user interfaces. The mxml user interface files are separate from the mediator classes that manage them.
The controller manages commands, pulling the strings on the view mediators and model proxies.
Enables the application to have an API
-------------------------------------
Commands can be dispatched from anywhere in the application.
The mediators, which manage specific user interface views, provide a public interface to their views.
Allows use of Flex modules (not sure about this one)
-------------------------
Apparently, Cairngorm has problems when code is modularized. PureMVC has better support for using Flex modules.
Consistent MVC pattern improves coherence of project
----------------------------------------------------
Once the MVC pattern is understood, it’s easier to figure out the workings of unfamiliar code that follows the pattern. You know where to look for code to control the user interface and code to manage value objects, etc.
|
