0

I wanted to understand the role of Controller in Javascript MVC patterrns. Is it one way or both way i.e. is the Controller responsible for keeping both Models and Views in sync or is it just responsible for updating models when the view changes? OR is it framework specific ?

Also in all frameworks, do we rquire to have View Controller pair for each element being displayed on screen ?

Improve this question

1 Answer 1

Reset to default
1

The thing to keep in mind with MVC is that it's intended to promote a "separation of concerns" that keeps your code relatively clean and untangled. In my experience there is not necessarily a "right" answer to many MVC questions, especially in JavaScript.

I've worked on a few big HTML/JavaScript applications, and I've had the most luck with this approach:

  1. "Model" objects that hold data and enforce some degree of business logic. This may involve some logic to sync changes to and from the server.
  2. "View" components that can easily be updated from the client. For example, custom jQuery controls that encapsulate different UI elements, wich as little business logic as possible.
  3. Perhaps an event mechanism by which the model notifies the rest of the system of changes to the underlying data. This is mainly to avoid having the model worry about how the data is used.
  4. A "Controller" that mutates the model in response to user actions.

Generally all the ugly code winds up in the controller, which is fine. At least the rest of the system is organized in a modular and understandable way. :) In the end, it's all about managing complexity.

Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.