Comments on: WPF patterns : MVC, MVP or MVVM or…?

By: jbe

jbe — Sat, 26 Jun 2010 15:58:19 +0000

Hi Alexander,

What for is the Controller needed? You might have a look at this article: http://waf.codeplex.com/wikipage?title=Model-View-ViewModel%20Pattern&ProjectName=waf

By: Alexander

Alexander — Sun, 08 Nov 2009 07:36:26 +0000

Hi, good article but..
You have described View, ViewModel and Model components of MVVM pattern. But what for is Controller needed on the picture? Can u describe?

By: Daniel Edstrom

Daniel Edstrom — Mon, 02 Nov 2009 19:14:14 +0000

Great info, I’ll go with this design pattern 4 sure

By: DataModel and ViewModel | Thought Clusters

DataModel and ViewModel | Thought Clusters — Fri, 14 Aug 2009 19:18:36 +0000

[...] WPF Patterns: http://www.orbifold.net/default/?p=550 [...]

By: Matias Bonaventura’s Blog Ã‚Â» Blog Archive » Prism Automation: Templates for implementing the MVVM pattern using the Composite Application Library

Thu, 13 Aug 2009 21:14:07 +0000

[...] WPF patterns : MVC, MVP or MVVM orâ€¦? [...]

By: aviade

aviade — Mon, 10 Aug 2009 21:00:34 +0000

Hi tony, It’s incorrect to say that in ‘MVP’ the view does not know anything about the presenter or the model.

About the relationship between the view and the presenter: MVP imposes no restriction on the kind of coupling between the view and the presenter, this is for the developers to decide. Personally, I prefer that the view will hold reference the presenter instance so it can directly invoke the appropriate method when user input arrives. DEREK GREER wrote fantastic article about the subject, please refer to:
http://www.ctrl-shift-b.com/2008/11/model-view-presenter-styles.html

About the relationship between the view and the model â€“ there are two flavors of MVP, ‘Passive View’ and ‘Supervising Controller’, in ‘Passive View’ the view is passive and has no link to the model just like you said, however, in ‘Supervising Controller’ the view has link to the model. You can read all about it at:
http://aviadezra.blogspot.com/2008/10/model-view-presenter-design-pattern.html

Regards, Aviad

By: MVC, MVP, and MVVM « WPF design and research

MVC, MVP, and MVVM « WPF design and research — Thu, 18 Jun 2009 21:34:56 +0000

[...] MVC, MVP, and MVVM By billbelliveau Comparing MVC, MVP, and why MVVM Article: http://www.orbifold.net/default/?p=550 [...]

By: Summary 06.05.2009 « Bogdan Brinzarea’s blog

Summary 06.05.2009 « Bogdan Brinzarea’s blog — Tue, 05 May 2009 11:45:43 +0000

[...] http://www.orbifold.net/default/?p=550 [...]

By: tony

tony — Sat, 07 Mar 2009 23:22:32 +0000

First, I think the driving motivation for MVVM is that data binding is so central to the design of WPF. It is hard to build MVC/MVP when using data binding extensively.

Second, I disagree with Francois. In MVP, the view does not know anything about the presenter or the model. In MVVM, the view binds directly to the model, which is a significant difference. Generally that should not be a problem because presumably the framework data binding is well tested.

By: Francois Vanderseypen

Francois Vanderseypen — Mon, 16 Feb 2009 13:32:34 +0000

Looks cool Pierre, well done! Nice website presentation as well.