ZF2是否基于MOVE? [英] Is ZF2 based on MOVE?
问题描述
我想知道ZF2是否完全基于MOVE而非经典MVC.
I'm wondering if ZF2 is based entierly on MOVE instead of the classic MVC.
我在某处阅读的内容确实基于MOVE(http://cirw.in/blog/time-to-move-on)，但例如在入门教程"(http://zf2.readthedocs.org/en/latest/user-guide/overview.html)中，他们说的是使用模型-视图-控制器范例创建简单的数据库驱动的应用程序".
Somewhere I read that is really bases on MOVE (http://cirw.in/blog/time-to-move-on) but e.g. in the "getting started tutorial" (http://zf2.readthedocs.org/en/latest/user-guide/overview.html) they are saying "creating a simple database driven application using the Model-View-Controller paradigm".
那么，它现在基于什么呢?两者都支持吗?
So, what is it now based on? Does it support both?
我有点困惑. ZF1和ZF2在MVC上有什么区别?
I'm a bit confused. What are the difference at MVC between ZF1 and ZF2?
谢谢
推荐答案
MOVE (Models, Operations, Views and Events)
MVC (Models, Views, Controllers)
MVC的问题是您最终将太多的代码填充到控制器中， 为了克服这个问题，MOVE是zf2项目中另一个可供选择的选项， 因为在这种体系结构中，您可以将控制器分为事件和操作.
The problem with MVC is that you end up stuffing too much code into controllers, to overcome this problem MOVE is another possible option to choose in zf2 projects, Because in this architecture you can split your controller into Events and Operations.
问题:ZF2是否完全基于MOVE架构?
我不认为ZF2是完全基于MOVE架构设计的. ZF2遵循 SOLID面向对象的设计原则，其松散耦合的
I don't think ZF2 is designed entirely on MOVE architecture. ZF2 follows the SOLID object oriented design principle with loosely coupled MVC architecture which provide more flexibility in terms of usability.
问题:我可以使用ZF2中的MOVE架构开发我的项目吗?
是的ZF2为您提供支持两种体系结构(MOVE，MVC)的所有功能. 它提供了模型，视图，控制器(操作)，事件. 开发人员将决定使用哪种架构.
Yes ZF2 provides you with everything to support both architectures (MOVE, MVC). It provides Models, Views, Controllers(Operations), Events. It is up to the developer which architecture he would like to use.
这篇关于ZF2是否基于MOVE?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
