MVVM, a WPF UI Design Pattern | The Continuum Show

Minh
WOOH! WOOH!

Can we have a 1-paragraph about this design pattern? You know... in this post?

edit:
harsh comment removed... Just frustrated that site was down again this morning.

wkempf

In reply to Minh

#Jan 19th @ 9:45 AM

It's complex enough, that there's no end to variations on the pattern. MVC, MVP, MVVM, Presentation Model (MVVM is actually just PM with a different name), Passive View, and so on. The general idea in each case though is to simply partition your classes around specific responsibilities. The View is responsible only for display, the Model is responsible for business/domain logic and the Poo (http://www.drwpf.com/blog/Home/tabid/36/EntryID/27/Default.aspx) is responsible in various ways (the variation in all of those patterns) for coordinating between the View and the Model. There's as close to a 1-paragraph description as your likely to get. From there, it's time to do a LOT of research. Tongue Out

That said, you don't have to be an expert on this family of patterns to benefit from using it.

Minh
WOOH! WOOH!

In reply to wkempf

#Jan 19th @ 9:56 AM

See guys? The above text makes me WANT to watch the video. Thanks wizard wkempf.

stormideas
stormideas - expertly crafted web applications

We built out an extensive Silverlight 2 collaboration application using the standard code-behind model, you can check it out at:

http://www.colaab.com

and while we think we've built a high quality product some of the lessons we learned are pushing us to use MVVM pattern for building out additional functionality.

There's a good set of links regarding the MVVM pattern in this StackOverflow question:

http://stackoverflow.com/questions/375301/should-i-use-the-model-view-viewmodel-mvvm-pattern-in-silverlight-projects

Thanks,

Bob

--
Bob Thomson
storm ideas

http://colaab.com
http://blog.stormideas.com
twitter: movingforwards

AdamKinney
Agent of Change

In reply to Minh

#Jan 19th @ 10:05 AM

Thanks for the suggestion Minh. Especially since this was meant as an introduction to the pattern, I probably should have put more detail into the introduction. Thanks wkempf and Bob for adding some context.

Hal Diggs

Well it's enough to "whet" my appitite. Looking forward to hearing more. Sorry I can't make the training in Cali... come visit Texas sometime Smiley

Svavar9

This reminds me of when I used XSLT for (X)HTML output.

Basically I'd have a server control that took an XSLT for display rather than using a user control with a code-in-front. I would then serialize the object I wanted to display into XML and pass it to the XSLT. The nice thing was that I could use the same C# code for an RSS feed, an HTML list on a page, and a JSON feed to name a few just by swapping out XSLTs.

I imagine WPF is way more elaborate with the 2-way databinding though.