问题描述
背景
我学习MVVM，并发现它的伟大的显示数据/模型。
I am learning MVVM, and found that it's great in displaying data / model.
但
我认为，这不仅有利于显示一个简单的模型，不是说好要显示一个复杂的模型。
I think, it's only good for displaying a simple model not that good to display a complicated model.
问
这是真的，MVVM有一定的局限性（编号列表或链接将是巨大的），还是我错构造模型，因为MVVM已经是通用的，任何情况下？
Is it true that MVVM has certain limitation (a numbered list or link would be great) or am I wrongly construct the model since MVVM is already versatile under any circumstances?
在限制我的意思是专注于如何在模式应该作出限制。
The "limitation" I meant is focused on the limitation on how the model should be made.
我之所以作出这个职位是因为我觉得有很多的障碍在构建我的应用程序显示在MVVM方式。
The reason I make this post is because I feel a lot of obstacle in constructing my application display in MVVM way.
ETC
是否有任何其他的模式旁边MVVM在WPF使用？
Is there any other pattern beside MVVM to use in WPF?
顺便说一句，对不起，如果这是一个不明确什么是问的问题。
Btw, sorry if it's a "not clear what is asked" question.
在情况下，它需要的，我的案例是我想提出一个简谱分数作家。请不要问没人用编号系统，何必呢？。在我的国家，它仍然普遍使用。
In case it's needed, my "case" is I am making a numbered musical notation scores writer. Please don't ask "no one use numbered system, why bother?". In my country, it still commonly used.
推荐答案
这听起来好像你需要阅读更多MVVM教程给我。 MVVM是一种开发方法，而不是一个平台。有没有规定使用MVVM来开发WPF应用程序，但这样做往往简化了整个过程。 MVVM有没有关系到一个项目的大小，可能除了它适合，因为所需的所需的基本框架，更大的应用程序更好。
It sounds as though you need to read some more MVVM tutorials to me. MVVM is a development methodology, not a platform. There is no requirement to use MVVM to develop a WPF Application, but doing so often simplifies the whole procedure. MVVM has no relation to the size of a project, except maybe that it suits bigger applications better because of the required basic framework required.
复杂的模型可以很容易地显示为简单的模型。这是完全有可能在父视图模型子视图模型，或只是巨大的视图模型，如果这是你的preference。 MVVM只是一种方法来实现关注的的分离的原理和真的不一样复杂一些做出来的人。
Complicated models can be displayed just as easily as simple models. It's entirely possible to have child view models in parent view models, or just huge view models if that's your preference. MVVM is just a way to implement the Separation of Concerns principle and really not as complicated as some make it out to be.
您有一个数据模型，这是直接被考虑到模型中使用的业务类别，无论是或包裹在其他视图模式，你preFER，这些视图模型绑定到视图来显示数据，并提供用户输入。还有的实在没有多少比这一点。
You have a data model, which are business classes that are used in view models, either directly or wrapped in other view models as you prefer, and those view models are bound to views to display the data and provide user input. There's really not much to it than that.
这篇关于什么是MVVM限制？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！