Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Design Patterns
Message
General information
Forum:
ASP.NET
Category:
Other
Title:
Miscellaneous
Thread ID:
01460935
Message ID:
01461119
Views:
60
Here's what this is all about....

I got hired at a new job. They sent me a link to this http://msdn.microsoft.com/en-us/magazine/dd419663.aspx and they asked me
to be familiar with it.

The article says that the Model-View-ViewModel pattern is base off the Model-View-Presenter pattern, which is in turn based off
the Model-View-Controller pattern. So I was reading all these articles trying to understand some history and also to understand
the terminolgy.

I get that the Model is the database, and from what I can see the View is the UI. But some portions of these articles seem to
seperate the UI into more than one part.

Then there's the Presenter and Controller. From what I can see they represent events occuring somewhere.

I'm a bit lost here.




>>Thanks.
>>
>>I'm looking at this wite here - http://www.enode.com/x/markup/tutorial/mvc.html
>
>FWIW if you are looking at this from a WPF POV stick to MVVM - it's far better suited to WPF than the MVC pattern because it makes it easier to build the complete view in XAML if neccessary (i.e. no code behind needed in the View)
>
>>
>>I'm having a hard time understanding what these pieces represent. I get the Model. That appears to be the data layer. But the View
>>and Controller portions are throwing me.
>>
>>
>>
>>>I neglected to point out that some design patterns are documented on the Fox Wiki. There is also info on Wikipedia. And to be obvious, a web search will bring up lots of stuff.
>>>
>>>
>>>>Thanks Craig. Good info.
Everything makes sense in someone's mind
public class SystemCrasher :ICrashable
In addition, an integer field is not for irrational people
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform