What is the difference between controller in MVC pattern and presenter in MVP pattern?

In MVP the Presenter assumes the functionality of the "middle-man" (played by the Application Controller in MVC). Additionally, the View is responsible for handling the UI events (like mouseDown, keyDown, etc), which used to be the Controller's job. Eventually, the Model becomes strictly a Domain Model.

Says Wikipedia.

Here is a more detailed explanation on the differences between the two.

See also Martin Fowler's Retirement note for Model View Presenter.

In MVC, the view is updated only by the model (by listening to its events). It is never updated by the controller. This is problematic when you need to format model data for the view, hence the need for MVP.

In MVP-Passive View, the view is updated only by presenter (presenter sets view properties). The presenter listens to events on the model [modifying the data if required] prior to updating the view.

In MVP-Supervising Controller, the view is updated by either the model or the presenter. If no formatting is required, the view updates itself via the model. If formatting is required, it updates itself via the presenter.