A week ago was the Throne of JS conference in Toronto, perhaps the most interesting and different conference I’ve been to for a while.
(Updated: 2013-02-02, 2013-11-24) Brief Background (optional reading) An Intro to Backbone.js: Part 1 – Models and Collections - Liquid Media. This is Part 1 of a series of tutorials.
In this series on Backbone.Marionette, we’ve already discussed Application and Module. This time, we’ll be taking a gander at how Marionette helps make views better in Backbone. Marionette extends the base View class from Backbone to give us more built-in functionality, to eliminate most of the boilerplate code and to convert all of the common code down to configuration. I highly recommend that you go back and read the articles about Application3 and Module4 first, if you haven’t already. Event Binding Up until recently, Backbone views were often mishandled, causing a horrible problem known as “zombie views.”
Many Backbone extensions and plugins — including Marionette — remedied this early on. This accomplishes the same thing as using listenTo, except it requires less code. A Thorough Introduction To Backbone.Marionette (Part 3) Backbone.js Tutorials. Introduction to Backbone.js. Introduction The web application development process has been evolving over the years.
These applications were targeted at a single user and ran on their operating systems. The major differentiating factor for these two applications was that the distributed applications provided an interactive user experience whereas web applications provided very limited features (due to technology limitations). Both these approaches had pros and cons and something needed to be done to get the best of both worlds. Then came the time when browsers became more capable and HTML became more mature. So why should we write single page apps when they lead to bad code?