No we’re not actually making a movie about View Model. If we were I am sure we’d get a low turn-out. :-) However it did get your attention.
What we are doing is some serious exploration into how we can help from a platform perspective folks that are implementing ViewModel (AKA Model-View-ViewModel AKA Presentation Model) in their Silverlight and WPF applications.
In the sense of a movie production, we’re in the script-writing phase. Here’s the general background.
There have been many a post on the importance of ViewModel as a pattern and the benefits it brings. In that there is little disagreement that it benefits both developers and designers.
For developers it allows them to have clean separation of presentation logic from the UI rendering, thus making the app easier to maintain. It removes code from the code-behind that often makes the UI logic difficult to test.
For designers it provides a way for a designer to completely change the look of the UI in a tool such as Expression Blend, without breaking the application functionality. Furthermore it gives the designer freedoms beyond simple look and feel, to actually decide which data elements are exposed, as well as defining the interactions between the UI elements through commands and attached behaviors.
Although the benefits of ViewModel are known, there’s quite a lot of debate both inside and outside Microsoft on the roles the developer and designer play in developing applications that use the pattern. This runs the spectrum from the designer having complete control of every aspect of the UI, to the development team having more of a tight handle on the UI components, and the designer being responsible for skinning. In either case there are tradeoffs.
What is your experience with ViewModel today?
Like any movie, we need to touch on the right nerves in order to make it a box-office hit. We need your feedback so we can complete the script.
Thanks for your help