- What is it in WPF and Silverlight that makes MVVM suit them so well?
- What is it in C++, or what does C++ lack, that makes MVVM and C++ never be mentioned together?
What is it in WPF and Silverlight that makes MVVM suit them so well?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
MVVM (Model – View – ViewModel) is an adaptation of the MVP (Model -View – Presenter) or MVC (Model – View – Controller) patterns, both of which are very popular design patterns for C++ applications. The main changes to the design pattern are to better support WPF and Silverlight so it isn’t so much that WPF suits MVVM, more that MVVM suits WPF.
Primarily the changes revolve around cleanly supporting the binding and command architecture present in the XAML technologies through use of
INotifyPropertyChangedandICommandobjects. Once again these changes wouldn’t help in C++ since it doesn’t have any native support for these high-level concepts. That isn’t to say that you couldn’t mimic all this functionality in C++, but on the way you would pass through using a basic MVP/C pattern and in most cases that is “good enough”.