Separate Visual Markup from Programming Logic

In a normal application, employing programming design pattern concepts such as Model-View-Controller (MVC) allows developers to separate programs into logical chunks. In MVC’s case, program logic is separated into the base data sources (model), the data visualization (view), and the program event handlers, data request, and flow logic (controller). If you follow design pattern precepts, switching containers with different visual/markup standards simply means having to swap out the view—instead of having to rewrite program logic, event handlers, and data transitioning flows, as would be the case with an embedded visual/programming logic.

Get Programming Social Applications now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.