70
95.9
Jun 02, 2010
Hi,
For more information visit this link: http://www.codeproject.com/KB/architecture/ModelViewPresenter.aspx
[]'s Iter Lubnon, Brazil.
70
95.7
Jun 28, 2010
Hello,
First try to understand what is MVP.I am giving some links.Go through that
http://msdn.microsoft.com/en-us/magazine/cc188690.aspx
http://msdn.microsoft.com/en-us/library/ff647543.aspx
Sample: Go through this link.it will give fair idea as to how make layers and proper implementations.
http://blog.vuscode.com/malovicn/archive/2006/10/10/Model-View-Presenter-_2800_MVP_2900_-pattern.aspx
60
95.3
Jul 18, 2010
To cut the explanation short, this is my understanding so far...
MVP = Model - View - Presenter
The basic idea behind it is to separate concerns between the layers. Clean separation enables better testability and easier maintainability and to separate responsibilities of each layer so that it can be readily replaced by another technology(eg. replacing winforms view with html view etc...)
Model - Being the data - class to hold data (domain object)
View - The UI - be it winforms / xaml / html (web forms) etc...
Presenter - Acts like a controller of the view, where business logic resides.
I think there are two main versions of MVP, active and passive, one having the model exposed to the view, and the other having the model exposed only via the presenter.
Still a newbie, but thats my understanding so far...
Cheers