So far we’ve been working on a simple one page application. Now we want to introduce another page – the dashboard.
We are now manually triggering events. But what about events that we don’t manually trigger? What happens when something changes without our interaction but we still need to respond to it?
So far our simple Backbone application doesn’t actually do anything. We will change this with Events.
Now the static fallback content has been created and is working, we can start to lay a basic Backbone application over the top.
This series of posts is the culmination of my experimentation, problems faced, decisions made and lessons learned when playing around with BackboneJS to build reactive sites.
After playing around with CoffeeScript, I find it is too good not to use. So now I am a CoffeeScript coder. Does this mean I’m a hipster? How embarrassing.
Installing NodeJS v0.4.0 on Arch Linux when you have both Python v3 and Python v2 installed