“你好世界”在MVC模式中
在面试某家公司的时候,我被问到了这个问题。
你知道哪些设计模式...然后我被告知基于 MVC 设计模式编写最简单的“hello world”应用程序。
后来我想出了一个 JavaScript 程序,
var arr = ["a","b","c","d"]; // this is an array, same as store or model
alert(arr[0]); // this is controller
//and browser alert is a view.
我被告知警报是一个视图。我所知道的关于 MVC 的基本概念是模型中的任何更改都会报告给视图。中间有一个控制器来调用这些方法。
您能否纠正我的方法,或者为 hello world MVC 应用程序提出替代解决方案。还解释了 MVC 的微妙方面。
谢谢。
In an interview for some company, I was asked this question.
What design patterns do you know...then I was told to write simplest "hello world" application based on MVC Design Pattern.
I came up with a JavaScript program
var arr = ["a","b","c","d"]; // this is an array, same as store or model
alert(arr[0]); // this is controller
//and browser alert is a view.
later I was told that alert is a view. The basic concept about MVC I know is any changes in Model are reported to View. And there is a controller in between to call the methods.
Can you correct my approach, or come up with an alternate solution for hello world MVC application. Also explain subtle aspects of MVC.
Thanks.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(6)
控制器 (
C
) 监听某种交互/事件流。在本例中,它是页面的加载事件。模型 (
M
) 是数据源的抽象。视图 (
V
) 知道如何渲染模型中的数据。控制器告诉视图使用模型中的某些内容执行某些操作。
在这个例子中,
请注意,上面的示例是为了演示目的而进行的严格简化。对于 JS MVC 世界中的“真实”“hello world”示例,请查看 todoMVC
Controller (
C
) listens on some kind of interaction/event stream. In this case it's the page's loading event.Model (
M
) is an abstraction of a data source.View (
V
) knows how to render data from the Model.The Controller tells to View to do something with something from the Model.
In this example
Note the above example is a severe simplification for demonstrating purposes. For real "hello world" examples in the JS MVC world go take a look at todoMVC
更好的例子
Better Example
MVC架构
我写过一篇关于MVC架构的文章。这里仅提供一些代码,希望有人发现它有帮助。
从上面的例子中可以看出,这个设计中有三个不同的单元,每个单元都有一个特定的工作要执行。让我们从上面的基础结构构建MVC设计。可以有多个视图和观察者,这里只先创建另一个视图。
这里要理解的是,模态不能依赖于视图或查看者或对数据执行的操作。数据模式可以独立,但需要视图和控制器,因为一个需要显示数据,另一个需要操作数据。因此,视图和控制器是由于模态而创建的,而不是相反。
从上面可以看出,视图和控制器之间已经建立了链接。这也是MVC模式的要求之一。为了演示模态中的更改,让我们更改程序并观察模态状态的更改是独立完成的并反映在视图中。
当模态的状态发生更改时,控制器已将消息发送到视图以更新自身。这很好,但仍然有一个主要概念需要实现,那就是观察者或控制器需要由 modal 来识别。为了看到这种情况的发生,模态和控制器之间必须有一个链接,以便任意数量的控制器可以表现出对模态的兴趣,这被视为将观察者注册到模态。这种关系是利用观察者不存在于空中的概念来实现的。它的存在是因为对模态感兴趣,因此在创建它时,必须使用它需要表现出兴趣的模态来创建它,或者换句话说,它可以访问该模态。让我们看下面的例子,看看如何使用 JavaScript 简单而优雅地实现这种 MVC 设计模式。
从上面可以看出,观察者已经使用模态 addObsever 函数注册了自己,并建立了到模态的链接。创建所有实例后。手动更改模态状态以在视图中显示效果。通常在 GUI 环境中,更改通常是通过用户按下任何按钮或通过任何其他外部输入来完成的。我们可以模拟随机发生器的外部输入并观察效果。在下面的示例中,在数据中添加了更多元素以清楚地显示效果。
上面的示例演示了 MVC 框架的使用,其中模态保持独立于视图和控制器。代表数据的模态负责通知所有已表现出兴趣并在模态中注册的相关方。一旦发生任何变化,就会向各方发送通知,并由他们采取行动。下面的示例与上面的示例略有不同,其中观察者仅显示新添加的数据。
人们可能想要添加的最后一件事是在不需要时删除观察者。这可以通过在模态调用中添加一个名为
removeObserver(object)
的方法来完成。上面的 MVC 设计模式可以通过使用子类和在顶级类中提供通用功能来更加细化,从而使设计尽可能简单,但它被留在了其他文章中。希望有帮助。MVC Architecture
I have written an article about MVC architecture. Here is only some code present,hope anyone finds it helpful.
From the above example just understand that there are three different units in this design where each has a specific job to perform. Let's build the MVC design from the above infra structure .There can be more than one view and Observer, here only another view is created first.
What is understood here is that the modal must not be dependent upon either the view or viewers or the operations performed on the data. The data modal can stand alone but the view and controller are required because one needs to show the data and the other needs to manipulate it. Thus view and controller are created because of the modal and not the other way round.
From the above it can be seen that there has been a link established between view and the controller. And this is one of the requirement of MVC pattern. To demonstrate the change in the modal let's change the program and observe that change in the state of modal is done independently and reflects in view.
When the state of the modal is changed the controller has sent the message to the view to update itself. It is fine, but still one main concept is left to be implemented and that is the observer or controller needs to be identified by the modal . In order to see this happening, there has to be a link between modal and the controller so that any number of controller can show the interest in the modal, this is considered as registering the observer to the modal. This relation ship is implemented using the concept that observer does not exist in the air. Its existence come because of having interest in the modal thus when it is created it has to be created using the modal that it needs to show interest or in other words it has an access to the modal. Let's look at the example below and see how this MVC design pattern is achieved simply and elegantly using JavaScript.
From the above it can be seen that the observer has register itself using modal addObsever function and establishes a link to the modal. Once all instances are created. Modal state was changed manually to show the effect in the view. Typically in GUI environment, the change is usually done either with a user pressing any button or from any other external input. We can simulate the external input from the random generator and observe the effect. Here in the example below, some more elements are added in the data to show the effect clearly.
The above example demonstrates the use of MVC frame work where a modal is kept independent of the view and and the controller. The modal representing the data is responsible of notifying all the interested parties that has shown the interest and registered themselves with the modal. As soon as any change happens notification is send to the parties and action is left upon them. The example below is slightly different from the above where only newly added data is shown by the observer.
The last thing which one may like to add is to delete the observer when not needed.This can be done through adding a method called
removeObserver(object)
in the modal calls. The above MVC design pattern can be more refined by using subcalssing and having common function present in the top class making the design as simple as possible but it is left on some other article. Hope it helps.MVC 是一种应该用于构建应用程序的设计模式。 MVC 代表模型、视图、控制。它基本上是说您应该将业务逻辑(模型)与用户界面(视图)和控制逻辑分开。
例如:
你有一个用户类,它从数据库加载用户,可以保存他们。这是你的模型。
您有一个使用 User 类来登录用户的控制器。
控制器完成后,它会显示一个包含文本“Welcome $username”的模板。
另外,模型不应该知道视图和控制器,视图不应该知道控制器,而控制器知道模型和视图。
关于 MVC 的维基百科:http://de.wikipedia.org/wiki/Model_View_Controller
MVC is a design pattern that should be used to structure your application. MVC stands for Model, View, Control. It basically sais that you should separate your business-logic (Model) from your User Interface (View) and your Control-Logic.
For example:
You have a user class, that loads users from the database, can save em. This is your model.
You have a Controller that uses the User class to log a user in.
After the controller is done, it displays a Template containing the Text "Welcome $username".
Also, the Model should not know about the View and the Controller, the View should not know about the Controller, whereas the Controller knows about the Model and the View.
Wikipedia on MVC: http://de.wikipedia.org/wiki/Model_View_Controller
我认为你有点没有抓住重点。
MVC 是一种用于设计应用程序的模式。我认为至少您希望能够更改模型,并看到视图中反映的更改。
您通常有一个对象来表示模型,另一个对象来表示“视图”(它可能在模型和用作视图的 HTML 对象之间进行中介)和一个控制器,它将接受输入从 HTML 对象中获取并更新模型。
因此,您更改编辑字段,编辑字段告诉控制器,控制器更新模型,模型触发控制器用来更新依赖于该数据的任何其他视图组件的事件。
实现“hello world”版本还需要几行,但我认为这就是我从这样的面试问题中寻找的内容。
I think you're kind of missing the point here.
MVC is a pattern you'd use for designing an application. I think at the minimum you'd expect to be able to change the model, and see the change reflected in the view.
You'd typically have an object to represent the model, a different object to represent the "view" (which would probably mediate between the model and the HTML objects that you're using as the view) and a controller, which would take inputs from your HTML objects and update the model.
So you change an edit field, the edit field tells the controller, the controller updates the model, the model fires events that the controller uses to update any other view components that depend on this data.
It'd be a few more lines to implement a "hello world" version, but I think this is what I'd be looking for from an interview question like this.
因此,我制作了一个简单的示例 MVC,数据输出在
console.log()
处。So I made a simple example MVC with data output at
console.log()
.