|
Model–view–presenter (MVP) is a derivation of the model–view–controller (MVC) architectural pattern, and is used mostly for building user interfaces. In MVP the ''presenter'' assumes the functionality of the "middle-man". In MVP, all presentation logic is pushed to the presenter.〔https://developers.google.com/web-toolkit/articles/testing_methodologies_using_gwt〕 == Pattern description == MVP is a user interface architectural pattern engineered to facilitate automated unit testing and improve the separation of concerns in presentation logic: * The ''model'' is an interface defining the data to be displayed or otherwise acted upon in the user interface. * The ''presenter'' acts upon the model and the view. It retrieves data from repositories (the model), and formats it for display in the view. * The ''view'' is a passive interface that displays data (the model) and routes user commands (events) to the presenter to act upon that data. Normally, the view implementation instantiates the concrete presenter object, providing a reference to itself. The following C# code demonstrates a simple view constructor, where ConcreteDomainPresenter implements the IDomainPresenter interface: public class DomainView : IDomainView The degree of logic permitted in the view varies among different implementations. At one extreme, the view is entirely passive, forwarding all interaction operations to the presenter. In this formulation, when a user triggers an event method of the view, it does nothing but invoke a method of the presenter that has no parameters and no return value. The presenter then retrieves data from the view through methods defined by the view interface. Finally, the presenter operates on the model and updates the view with the results of the operation. Other versions of model-view-presenter allow some latitude with respect to which class handles a particular interaction, event, or command. This is often more suitable for web-based architectures, where the view, which executes on a client's browser, may be the best place to handle a particular interaction or command. From a layering point of view, the presenter class might be considered as belonging to the application layer in a multilayered architecture system, but it can also be seen as a presenter layer of its own between the application layer and the user interface layer. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Model–view–presenter」の詳細全文を読む スポンサード リンク
|