Over 10 years of community discussion and knowledge are maintained here as a read-only archive.
In PureMVC the mediator is acting like a Presenter. And the controller remains with no direct access to the view.
MVP Presenter is a code-behind class, which acts like a puppet master to a view component with no intelligence of its own. It is too 'familiar' with the view component. -=Cliff>
how re-usable can View components really be anyway
how re-usable can View components really be anywayBottom line; Component developers don't need to understand the framework. -=Cliff>
Since views are templates they can also contain behavior. The most common behavior you encounter in a view is formatting; however, since the view is a template you will occasionally see computations or worse. Because this logic is stored in a template it can be problematic to test. Presenters address this problem by pulling all formatting, computation, and any additional behavior into a class that can be easily tested.
If PureMVC used Presenters, then that would mean anyone wanting to use your component needs to be using PureMVC.
How would one go about solving this problem in the PureMVC world?