I the add the view to the presenter via constructor injection:

ICustomerView customerView = new CustomerForm();
CustomerPresenter customerPresenter = new CustomerPresenter(customerView);

Inside the presenter i then hook up the events that the presenter needs from the view.. (e.g. “Save”)

Implementation gives a simple understanding :),

At first I had doubts with this pattern, but after gaining a deeper understanding of it I’ve realised how it enforces separation of view from model(controller). makes the view dumber which is a good thing.

Cheers
Sonny M

From the link:

Classic MVC doesn’t work well with modern rich client tools because they design things so that the view handles all the user events such as mouse and keyboard clicks. In Model View Presenter the view continues to handle these, but then immediately delegates these to the presenter. The presenter then decides what to do with the event, communicating with the domain and the data in the view’s controls.

The difference between MVP and class MVC is that in MVC the Controller changes the Model or the View and the View gets data from the Model. The model also updates the view when data changes.

Using MVP, the View only communicates with the Presenter. The presenter then communicates with both the View and the Model.

http://www.google.com/search?sourceid=navclient&ie=UTF-8&rls=GGLD,GGLD:2004-29,GGLD:en&q=model+controller+pattern