This article is within the scope of WikiProject Software, a collaborative effort to improve the coverage of software on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
The Model-View-Controller architecture is a clean way to organize interacting classes. For example, when I press the button over here, a series of changes takes place here, here, here, over here, and on the third page of the tab. Since MVC is foundational and eliminates a vast array of potential problems that would result from ad hoc organization, PureMVC is anything but trivial. It could be subsumed in an article on architectural design patterns, but it would get lost in such a vast topic. 220.127.116.11 (talk) 14:44, 3 January 2011 (UTC)
I would recommend removing the link to http://active.tutsplus.com/tutorials/workflow/understanding-the-puremvc-open-source-framework/. It's a confusing tutorial which example contradicts the intended use of the framework. In this example, view components use notificatIons to comunicate to mediators, states things like that a mediator is a class to add a component view to your base application, use always application class as the viewComponent argument for registering mediators, put conditionals in commands to detect which notification triggered them when they already know by registration sentence in the Application Façade, etc. Indeed it's not even following the loose coupling philosophy of an average MVC implementation, using constants defined in the view from the model to send notifications. Certainly not a good one, specially for a beginner trying to understand a difficult framework.