DBpedia – Linked Data Fragments

Matches in DBpedia 2015-04 for { <http://dbpedia.org/resource/Model_View_ViewModel> ?p ?o }

• Model_View_ViewModel abstract "The Model View ViewModel (MVVM) is an architectural pattern used in software engineering that originated from Microsoft as a specialization of the Presentation Model design pattern introduced by Martin Fowler. Largely based on the model–view–controller pattern (MVC), MVVM is a specific implementation targeted at UI development platforms which support event-driven programming, specifically Windows Presentation Foundation (WPF) and Silverlight on the .NET platforms using XAML and .NET languages. Technically different, but similar, Presentation Model design patterns are available in HTML5 through AngularJS, KnockoutJS,Ext JS,Vue.js, and for Java the ZK framework (Model-View-Binder).MVVM facilitates a clear separation of the development of the graphical user interface (either as markup language or GUI code) from the development of the business logic or back end logic known as the model (also known as the data model to distinguish it from the view model). The view model of MVVM is a value converter meaning that the view model is responsible for exposing the data objects from the model in such a way that those objects are easily managed and consumed. In this respect, the view model is more model than view, and handles most if not all of the view’s display logic (though the demarcation between what functions are handled by which layer is a subject of ongoing discussion and exploration). The view model may also implement a mediator pattern organising access to the backend logic around the set of use cases supported by the view.MVVM was designed to make use of data binding functions in WPF to better facilitate the separation of view layer development from the rest of the pattern by removing virtually all GUI code (“code-behind”) from the view layer. Instead of requiring user experience (UX) developers to write GUI code, they can use the framework markup language (e.g., XAML) and create bindings to the view model, which is written and maintained by application developers. This separation of roles allows interactive designers to focus on UX needs rather than programming of business logic, allowing for the layers of an application to be developed in multiple work streams for higher productivity. Even when a single developer works on the entire code base a proper separation of the view from the model is more productive as the user interface typically changes frequently and late in the development cycle based on end-user feedback.In 2005, John Gossman, currently one of the WPF and Silverlight Architects at Microsoft, unveiled the Model-View-ViewModel (MVVM) pattern on his blog. MVVM is identical to Fowler's Presentation Model, in that both patterns feature an abstraction of a View, which contains a View's state and behavior. Fowler introduced Presentation Model as a means of creating a UI platform-independent abstraction of a View, whereas Gossman introduced MVVM as a standardized way to leverage core features of WPF to simplify the creation of user interfaces. In that sense, I consider MVVM to be a specialization of the more general PM pattern, tailor-made for the WPF and Silverlight platforms.The MVVM pattern was conceived to support WPF and Silverlight, both pieces that debuted with the .NET Framework 3.0 which was released on 21 November 2006. This pattern is now being more broadly applied in other technology domains, such as happened with the earlier MVC or Model View Presenter (MVP) patterns.Several Microsoft architects working on WPF have written extensively about MVVM in online media, including creator John Gossman, Microsoft MVP Josh Smith, and Microsoft Program Manager Karl Shifflett.As the understanding of the pattern disseminates through the industry, discussion continues regarding what tools can be developed to support the pattern, selection of where to place different kinds of supporting code in the pattern, the best methods for data binding, and how to expose data within the view model, how appropriate the pattern is for use within JavaScript, and other topics.More recently the pattern has been described also as model-view-binder (MVB). This is the first reported implementation of the pattern outside of the Microsoft stack, namely using ZK/Java.Notable JavaScript implementations of this pattern include Knockout.js, Vue.js, etc.".
• Model_View_ViewModel thumbnail MVVMPattern.png?width=300.
• Model_View_ViewModel wikiPageExternalLink code.msdn.microsoft.com.
• Model_View_ViewModel wikiPageExternalLink How-to-implement-MVVM-71a65441.
• Model_View_ViewModel wikiPageExternalLink dd419663.aspx.
• Model_View_ViewModel wikiPageExternalLink ZkToDoViewModel.java.
• Model_View_ViewModel wikiPageID "23070896".
• Model_View_ViewModel wikiPageRevisionID "645332295".
• Model_View_ViewModel hasPhotoCollection Model_View_ViewModel.
• Model_View_ViewModel sign Josh_Smith.
• Model_View_ViewModel source "WPF Apps With The Model-View-ViewModel Design Pattern".
• Model_View_ViewModel text "In 2005, John Gossman, currently one of the WPF and Silverlight Architects at Microsoft, unveiled the Model-View-ViewModel pattern on his blog. MVVM is identical to Fowler's Presentation Model, in that both patterns feature an abstraction of a View, which contains a View's state and behavior. Fowler introduced Presentation Model as a means of creating a UI platform-independent abstraction of a View, whereas Gossman introduced MVVM as a standardized way to leverage core features of WPF to simplify the creation of user interfaces. In that sense, I consider MVVM to be a specialization of the more general PM pattern, tailor-made for the WPF and Silverlight platforms.".
• Model_View_ViewModel subject Category:Software_architecture.
• Model_View_ViewModel subject Category:Software_design_patterns.
• Model_View_ViewModel type Abstraction100002137.
• Model_View_ViewModel type Cognition100023271.
• Model_View_ViewModel type Form105930736.
• Model_View_ViewModel type PsychologicalFeature100023100.
• Model_View_ViewModel type SoftwareDesignPatterns.
• Model_View_ViewModel type Structure105726345.
• Model_View_ViewModel type Thing.
• Model_View_ViewModel comment "The Model View ViewModel (MVVM) is an architectural pattern used in software engineering that originated from Microsoft as a specialization of the Presentation Model design pattern introduced by Martin Fowler. Largely based on the model–view–controller pattern (MVC), MVVM is a specific implementation targeted at UI development platforms which support event-driven programming, specifically Windows Presentation Foundation (WPF) and Silverlight on the .NET platforms using XAML and .NET languages.".
• Model_View_ViewModel label "Model View ViewModel".
• Model_View_ViewModel label "Model View ViewModel".
• Model_View_ViewModel label "Model View ViewModel".
• Model_View_ViewModel label "Model-View-ViewModel".
• Model_View_ViewModel label "Modèle-Vue-VueModèle".
• Model_View_ViewModel seeAlso Presentation_layer.
• Model_View_ViewModel sameAs Model_View_ViewModel.
• Model_View_ViewModel sameAs Modèle-Vue-VueModèle.
• Model_View_ViewModel sameAs Model_View_ViewModel.
• Model_View_ViewModel sameAs m.064l14r.
• Model_View_ViewModel sameAs Q1247905.
• Model_View_ViewModel sameAs Q1247905.
• Model_View_ViewModel sameAs Model_View_ViewModel.
• Model_View_ViewModel wasDerivedFrom Model_View_ViewModel?oldid=645332295.
• Model_View_ViewModel depiction MVVMPattern.png.
• Model_View_ViewModel isPrimaryTopicOf Model_View_ViewModel.