Model-View-Controller
I want to talk about MVC (Model View Controller) with readers. MVC is not necessarily a technology, but a methodology - or a way of doing things. It involves a separation of concerns when creating a combined body of work. When it comes to standardized technologies vs informal methodologies, you're bound to come across various cases of the latter (methodologies) that sound like cases of the former (technologies).
For instance, we've discussed html(5) which happens to be a technology - a literal distinct tool, i.e., you can write things in html. However, dhtml (d for dynamic) is an informal methodology for combining different internet tools for creating an overall effect that updates the behavior of a webpage from the client-side (within the browser) after the page has been loaded. DHTML is a methodology. We can say the same thing about AJAX - asynchronous JavaScript and XML - where JS and XML are the technologies involved but AJAX is a methodology on how to use them together in a certain way.
Coming full circle, MVC works as follows:
In everyday web development, an example of MVC is the relationship between HTML5(Model), CSS3(View) - the latest iteration of the Cascading StyleSheets standard - and JavaScript(Controller). So far, you've been introduced to HTML5. Before HTML5, html had the holistic ability to post data to a web page and dictate its general appearance. However, the ability to augment the appearance of hypertext was far surpassed by the capabilities of Cascading StyleSheets, when compared to the abilities of html4 and lower. Hence, HTML5 made provisions to delegate the majority of this ability - this "view" component to CSS. In the next post, I will elaborate on the "view" component.
For instance, we've discussed html(5) which happens to be a technology - a literal distinct tool, i.e., you can write things in html. However, dhtml (d for dynamic) is an informal methodology for combining different internet tools for creating an overall effect that updates the behavior of a webpage from the client-side (within the browser) after the page has been loaded. DHTML is a methodology. We can say the same thing about AJAX - asynchronous JavaScript and XML - where JS and XML are the technologies involved but AJAX is a methodology on how to use them together in a certain way.
Coming full circle, MVC works as follows:
- The Model component has to do with data we wish to present.
- The View component is a description of how we wish to present the data in our model component.
- The Controller is our interactive component. If a user comes across the material in our Model component, what update might we make in our other 2 components or how might we attempt to interact with the user with a series of responses or interactions entirely defined within our controller segment.
In everyday web development, an example of MVC is the relationship between HTML5(Model), CSS3(View) - the latest iteration of the Cascading StyleSheets standard - and JavaScript(Controller). So far, you've been introduced to HTML5. Before HTML5, html had the holistic ability to post data to a web page and dictate its general appearance. However, the ability to augment the appearance of hypertext was far surpassed by the capabilities of Cascading StyleSheets, when compared to the abilities of html4 and lower. Hence, HTML5 made provisions to delegate the majority of this ability - this "view" component to CSS. In the next post, I will elaborate on the "view" component.
Comments
Post a Comment