Note
Good paper on two similar design patterns MVC and MVP. By reading this paper with its clear descriptions of these patterns, i reconfirmed my position that they have no place in RESTful web development. While most of the principles that these patterns are composed of are important, i prefer to think in GET, PUT, POST, DELETE and representations.
Quote
It is of course pretty tricky to replace one UI framework with another when the code browsers being used are themselves implemented in the framework being replaced.
It is the responsibility of the application model to be the mediator between the true domain objects and the views and their controllers.
In MVP, the model is purely a domain object and there is no expectation of (or link to) the user interface at all.
Hence, it was our original intention with MVP to have a View Composer for laying out the visual aspect of an application but to supplement this with a Schematic Composer which would be able to lay out the application logic as a schematic design. Such a Schematic Composer would automatically generate methods within the appropriate presenter classes to implement the schematic wiring’s behaviour.
|
|