关于angularjs:MVW代表什么?

What does MVW stand for?

Here's the content description for Angularjs page:

AngularJS is what HTML would have been, had it been designed for building web-apps. Declarative templates with data-binding, MVW, MVVM, MVC, dependency injection and great testability story all implemented with pure client-side JavaScript!

那么,什么是MVW站在那里?(Considering the MVC,MVW,MVP etc Squabble,I would be"whatever",model-view-whatever=p)


它确实代表任何事物,就像在任何对你有用的事物中一样。

MVC vs MVVM vs MVP. What a controversial topic that many developers
can spend hours and hours debating and arguing about.

For several years +AngularJS was closer to MVC (or rather one of its
client-side variants), but over time and thanks to many refactorings
and api improvements, it's now closer to MVVM – the $scope object
could be considered the ViewModel that is being decorated by a
function that we call a Controller.

Being able to categorize a framework and put it into one of the MV*
buckets has some advantages. It can help developers get more
comfortable with its apis by making it easier to create a mental model
that represents the application that is being built with the
framework. It can also help to establish terminology that is used by
developers.

Having said, I'd rather see developers build kick-ass apps that are
well-designed and follow separation of concerns, than see them waste
time arguing about MV* nonsense. And for this reason, I hereby declare
AngularJS to be MVW framework - Model-View-Whatever. Where Whatever
stands for"whatever works for you".

Angular gives you a lot of flexibility to nicely separate presentation
logic from business logic and presentation state. Please use it fuel
your productivity and application maintainability rather than heated
discussions about things that at the end of the day don't matter that
much.


为完整起见,以下是提及的缩写词:

MVC - Model-View-Controller

MVP - Model-View-Presenter

MVVM - Model-View-ViewModel

MVW / MV* - Model-View-Whatever

还有一些:

HMVC - Hierarchical Model-View-Controller

MMV - Multiuse Model View

MVA - Model-View-Adapter


Having said, I'd rather see developers build kick-ass apps that are
well-designed and follow separation of concerns, than see them waste
time arguing about MV* nonsense. And for this reason, I hereby declare
AngularJS to be MVW framework - Model-View-Whatever. Where Whatever
stands for"whatever works for you".

学分:AngularJS Post-Igor Minar


  • 网址:https://en.wikipedia.org/wiki/mvw
  • https://en.wikipedia.org/wiki/angularjs网站
  • https://angularjs.org网站/
  • AngularJS-超级英雄JavaScript MVW框架

  • https://plus.google.com/+angularjs/posts/aznvhj355g2
  • enter image description here


    我觉得mvv(model view whatever)或mv*是一个更灵活的术语,可以用来描述我认为AngularJS的一些独特之处。它帮助我理解它不仅仅是一个MVC(模型视图控制器)JavaScript框架,但是它仍然使用MVC,因为它有一个模型视图和控制器。

    它还可以被视为MVP(模型视图演示者)模式。在AngularJS中,我认为演示者是视图的用户界面业务逻辑。例如,通过使用可以格式化显示数据的过滤器。这不是业务逻辑,而是显示逻辑,它让我想起了我在GWT中使用的MVP模式。

    此外,它还可以是MVVM(模型-视图-模型),视图-模型部分是两者之间的双向绑定。最后,它是MVW,因为它还有其他的模式可以使用,正如@steve chambers所提到的。

    我同意其他的答案,在这些术语上学究可能是有害的,因为重点是从术语中理解概念,但同样的,充分理解术语有助于设计应用程序代码,知道去哪里和为什么。