wpf - Is MVVM pattern a symbiote of MVC + PAC patterns? -

i've surfed wikipedia , have found such article:

http://en.wikipedia.org/wiki/mvc4wpf

a part link upper:

mvc4wpf open-source, extensible, automated code pattern developed @ information control corporation windows presentation foundation (wpf) development based on model-view-controller (mvc) , presentation-abstraction-control (pac) patterns...

i know, wpf/silverlight use mvvm pattern: model-view-viewmodel.

so mvc4wpf first version of mvvm?

i don't know history of wpf/silverlight development well, mvvm has remind me sort of mvc.

and if it's true, mvvm = mvc + pac?

whenever see questions this, think dr. wpf's design pattern.

it doesn't matter want call separate concerns. hear lot of wpf people talk mvvm, boils down trying keep code separate. in mvvm, have:

• model data classes. knows nothing anything.
• view gotta show data. knows models, not how them. "knows" viewmodel through bindings. depending on how wire them together, may create viewmodel.
• viewmodel glue between view , model. can know view, or can best hide view viewmodel.

in mvc have:

• model data classes. knows nothing anything.
• view gotta show data. knows models, not how them.
• controller glue between view , model. knows view , model.

really, last bit changes (hence dr. wpf's mv-poo). , in wpf, bindings in xaml nice why want write bunch of code? call whatever want, easier in wpf if view knows bit poo.

having never used pac pattern, can't speak strengths, wikipedia, seems similar mvc. so, classify bit of mv-poo.

now, considering mvc4wpf hasn't had release since 2009 (and website documentation down of 7/6/13), suggest steer clear of it. can't speak strengths or weaknesses, if you'd mvvm framework, mvvm light , caliburn.micro both have support , great reviews.

i'd point out not applications need poo. mike hillberg put nicely.