The viewmodel exposes the data and command objects that the view needs You could think of this as a container object that view goes to get its data and actions from. Trying to grasp the concepts of mvvm, i have already read several blogs and looked at a few projects From what i understand, a view is dumb, it just knows how to present something that is passed. 在MVVM架构下，View 和 Model 之间并没有直接的联系，而是通过ViewModel进行交互，Model 和 ViewModel 之间的交互是双向的， 因此View 数据的变化会同步到Model中，而Model 数据的变化也会立即反应到View 上。 查看剩余 4 条回答 For something released a little more recently (last month), take a look at rainer stropek's video series mvvm in wpf and silverlight he flies right through it, but does an extremely good job of going from start to finish with an actual application.
比起MVP，MVVM不仅简化了业务与界面的依赖关系，还优化了数据频繁更新的解决方案，甚至可以说提供了一种有效的解决模式。 至此，我们能理解为什么许多人认为MVVM是最好的一种模式，没有之一。 但事实上， MVVM也是依赖于我们至今所讲的“特有的情境”。 MVVM与前后端关系 MVVM主要与前端开发相关，因为它处理的是用户界面及其交互逻辑。 在现代Web开发和移动应用程序开发中，MVVM架构模式经常被用来构建用户界面，特别是在使用Angular、Vue.js、React（配合相关库和模式）等前端框架时。 I am currently working with the microsoft mvvm template and find the lack of detailed examples frustrating The included contactbook example shows very little command handling and the only other e. I'm learning about flutter, and i have questions about implementing an mvvm architecture I'm uncertain how to handle the initialization logic for the viewmodel, particularly when using provider for.
What extra benefit we get by using this To be honest , today i had an interview and i have been asked this question Mvvm that said, let's dive into the topic of mvvm by means of an example
OPEN
