MVPVM - 使用Interface或Presenter进行事件处理

Question

Handling button click, row double click and other events. What is a better approach?

Direct Access of presenter to View. So the view can directly call the appropriate method on the presenter, eg. Presenter.Save()

Or

Event in interface.

interface ILoginDetailView:
{
   event EventHandler Save;        
}

View

private void btnSave_Click(object sender, EventArgs e)
{
   Save(this, null)
}

Presenter

view.Save += new EventHandler(view_Save);

I feel the 2nd approach is better as it makes the view decoupled from the presenter. But in all the articles/papers where the pattern is described, 1st approach is used.

Answer 1

Personally, I always go for the second approach. Generally, I don't like having the view know about the presenter, and the decoupling is a great advantage. Otherwise, I find myself making functions taking specific variables from the view. The event pattern breaks that nicely.

Answer 2

我也会采用第二种方法，因为正如你所说，将视图与演示者分离，这反过来使得这些东西可以测试。

Answer 3

In the MVPVM (model view presenter view model) pattern it's stated that the view is usually tightly coupled to your view. This allows your view-model, view, and business/data access layers to remain decoupled.

So once again, the presenter can be tightly to allow direct access to the view without adding responsibility to your view model or view.

MVPVM Design Pattern

It's a great article and discusses MVC, MVP, MVVM, and MVPVM verly well.

Answer 4

I think the first approach is much cleaner.

A Save just doesn't feel like an event . It's a direct action.

In MVVM you're calling a command on the viewmodel, in MVC you're calling an action on a controller and in MVP you're calling a method on the presenter.

A Saved or Saving is an event, but not Save .

But it's probably a question about personal preferences.