Talk:Model–view–viewmodel

Code samples

Please provide some code samples in Java and/or C. Learners often misunderstood patterns without code examples. — Preceding unsigned comment added by 191.250.203.132 (talk) 00:06, 7 December 2015 (UTC)

Impossible to read

Someone please hyphenate the word view-model, or make it a single word ViewModel and use that consistently across the article. It is impossible to read this as it is. Lacks consistency and readability. — Preceding unsigned comment added by 202.21.178.210 (talk) 08:03, 21 August 2013 (UTC)

Full of buzzwords

This page reads like something used internally at Microsoft to sell in a research project to upper management. It's full of buzzwords but it doesn't actually tell you anything useful about MVVM. 85.228.203.199 (talk) 15:14, 5 June 2011 (UTC)

What is MVVM?

...what is MVVM? The question remains unsolved. —Preceding unsigned comment added by 124.177.3.7 (talk) 02:06, 8 April 2011 (UTC)

About a Wikipedia login

I created a Wikipedia login and joined the biggest online community ever, just to say this:

... What???

Izhido (talk) 20:25, 11 February 2010 (UTC)

Open source MVVM frameworks

I suggest that the list is changed to a table with three columns. The list already contains two elements per element. One is the framework and one is the developer. I suggest the third is a summary. Today the list is merely a list of names and provides you with little information about the frameworks.

Jack Wester (talk 18:39, 15 December 2011 (UTC)

Is this relevant in anyway to Rich UIs / flex / Ajax / HTML5?

I am very keen to know, if flex/flash combination makes use of this pattern?

Also what are the commonly known/used products based on this model? (MS Sharepoint)

... and what about Lightswitch and HTML5?

J mareeswaran (talk) 05:37, 9 June 2011 (UTC)

Flex and OpenLaszlo

I don't know if Flex makes use of this, but OpenLaszlo (which was introduced a couple of years earlier, and with which Flex and MXML share many features such as data binding) does. I called this the Data-Driven Presentation (DDP) architecture in 2003, and this post briefly describes its use with OpenLaszlo. ows (talk) 13:16, 22 December 2011 (UTC)

Added content

The first line says MVVM is specific to WPF, which is incorrect I believe. It may be tied to XAML, but XAML also applies to Silverlight.

I have not yet changed the title, but I have added a considerable amount of content, including reuse of all of the previous citations and some of the language. Essentially, I added a more in-depth analysis of the pattern, added a history section, and linked to several pattern descriptions (both visual and text).

I am, admittedly, new to Wiki posts, but I have vetted the entry with several WPF software architects, who agree with the write up as it stands.

My apologies if I trod on any toes or lost any information with the additions!

Quidley (talk) 19:45, 5 June 2009 (UTC)

Additions and recommendations

I have some considerable additions and recommendations for this article.

First, the title should change to something like Model-View-ViewModel (MVVM) so that it (a) parallels the introduction to the MVC and MVP patterns, and (b) can be found by users searching for MVVM, which is a common means for referring to this architectural pattern. I almost began writing the article from scratch because I couldn't locate it and just happened to stumble into this article.

Second, I have a great deal of content to add regarding the nature of the pattern, its history, a description of the pattern, and controversies around its use. Anyone mind if I post these? I'll likely proceed by 05 Jun 2009 if there are no responses.

Thanks,

Quidley (talk) 18:59, 3 June 2009 (UTC)

Hebrew —Preceding unsigned comment added by 194.56.215.66 (talk) 16:40, 4 August 2009 (UTC)

Problem with this sentence

This sentence does not read well:

MVVM was designed to make use of specific functions in WPF to better facilitate the separation ...

It has to be read several times before understanding it. I recommend rewriting it. --Mortense (talk) 09:32, 30 January 2012 (UTC)

Microsoft Ripped off, they didn't "Pioneer"

It is clearly stated in the article that Martin Fowler originated this pattern and that Microsoft's version is "identical". Later it is claimed that Microsoft "Pioneered" this approach. Clearly, this could be no further from the truth; once again it is a clearly rebranded Microsoft dupe, they made no actual contribution here other than to obscure the work of a sole independent contributor. 156.34.158.128 (talk) 22:33, 1 July 2012 (UTC)

Model View Binder

This article is useful in explaining the idea of model-view-binder, which is quickly becoming an important variant of MVC, MVP and Controller-Mediated MVC. Reference to the fact that it is employed by Microsoft only strengthens that this previously hard-to-talk-about pattern is solidifying. I personally prefer the name Model-view-binder as a clearer way to show its intention. Tamstoker (talk) 08:54, 19 September 2012 (UTC)

I agree with Tamstoker that this should be called MVB. Iæfai (talk) 01:03, 19 November 2012 (UTC)

UML Diagram

This is after all a design pattern, could someone add a UML diagram or the like? — Preceding unsigned comment added by Msmith0957 (talk • contribs) 23:26, 2 January 2013 (UTC)

Model is not equal to business logic.

Model is not equal to business logic or back end logic. This sentence: "from the development of the business logic or back end logic known as the model" need more clarification. — Preceding unsigned comment added by 77.89.20.230 (talk) 11:56, 6 March 2013 (UTC)

my first question took half a page to find

I came to this page knowing what the MVC is, so all I wanted was a quick explanation of how MVVM differs from MVC.

I eventually found it, but halfway down the page. — Preceding unsigned comment added by Harvest316 (talk • contribs) 05:09, 19 July 2013 (UTC)

Hard to read and not understandable

Even the examples are not good. The C# example contains e.g. a property AddNewCustomer which is never used in the code. Instead it contains a method PerformAddNewCustomer. Sometimes the properties of the class are used and sometimes internal variables without accessors (variable i). The usage of this class within the GUI is missing completely. Do not know where and how to use this class. => no consistency, raises more questions than answers. — Preceding unsigned comment added by 178.7.225.16 (talk) 11:20, 22 August 2014 (UTC)

Not an architectural pattern

This article is totally incorrect and totally biased (alas, just as most articles in the same categories). To begin with, MVVM is not even an architectural pattern, it is a design pattern. (E.g. SOA is an architectural pattern.) 2.33.22.236 (talk) 09:04, 5 March 2017 (UTC)

Elephant in the room

Firstly, the name and the pattern don't match. The pattern is Model-ViewModel-View, but the name is Model-View-ViewModel. Secondly, the diagram at the top of the article is backwards, giving View-ViewModel-Model. We probably can't do anything about the misnaming of a famous pattern, but we could reverse that diagram. 192.31.106.35 (talk) 14:02, 24 May 2018 (UTC)

they're all the same

In my experience as a professional UI programmer, in MVC, the Model is fairly easy to identify; it handles the data, and is farthest back, in the direction of the database or store. The View is usually templates and the software supporting them (a more hazy distinction), usually the most user-facing piece. And then the Controller has always been the most amorphous; I think the best definition is "everything else".

In all cases, the MC and VC interfaces can move; a Model might do some processing to the data coming and going, and a View might have significant logic that would otherwise be in the Controller. Under these circumstances, I just don't see a significant difference between all these MV* variants. OsamaBinLogin (talk) 19:44, 19 November 2018 (UTC)

Conflicting sentences

In the opening paragraph, it states "MVVM was invented by Microsoft architects Ken Cooper and Ted Peters [...]". However later in the "criticism" section, it states "[...] MVVM creator John Gossman himself [...]".

Is John Gossman the creator or are Ken Cooper and Ted Peters? Whoever it is, this is conflicted and misleading. :(
Joedf (talk) 20:04, 28 February 2020 (UTC)