Mvvm design pattern
Download
1 / 4

MVVM Design Pattern - PowerPoint PPT Presentation


  • 216 Views
  • Updated On :

MVVM Design Pattern. O verview of the MVVM pattern for Silverlight and WPF. What is MVVM?. Part of the M-V-* family of separated presentation patterns (MVC, MVP, etc.) Stands for “Model-View- ViewModel ” Adaptation of Fowler’s “Presentation Model” “ Linqua Franca” of WPF and Silverlight.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'MVVM Design Pattern' - philyra


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Mvvm design pattern l.jpg

MVVM Design Pattern

Overview of the MVVM pattern forSilverlight and WPF


What is mvvm l.jpg
What is MVVM?

  • Part of the M-V-* family of separated presentation patterns (MVC, MVP, etc.)

  • Stands for “Model-View-ViewModel”

  • Adaptation of Fowler’s “Presentation Model”

  • “Linqua Franca” of WPF and Silverlight


What s a viewmodel l.jpg
What’s a “ViewModel”?

  • Is it a “View of the Model”? or …

  • A “Model of the View”?

  • I prefer Model of the View, or Model forthe View.

  • The VM is an abstraction of the state (bindings) and behavior (actions/commands) of the View.


View model as state machine l.jpg
View Model as State Machine

  • “When I’m constructing a system, I prefer to think of the VM as a state machine with the View being a visualization of the current state.  The user interacts with the View, causing “messages” (actions/commands/bindings) to be sent to the VM.  The VM receives and delegates or interprets these messages, which may or may not result in state changes and may or may not result in domain model interaction.” – Rob Eisenberg (Caliburn, NHProf)