The developer's primary background was writing thick client Windows applications. I figured the best place to start is to focus on the bare essentials and then work up to more advanced concepts and resources. I started to respond to the developer in an e-mail, but then I remembered what Scott Hanselman said in a recent post and video ... "Instead, consider writing a blog post or adding to a wiki with your keystrokes, then emailing the link to the original emailer. " So, I decided to make this blog post for the developer and also for anyone else who may be interested in similar resources. Backbone tutorial video. Build Environment. This new Backbone.js tutorial series will walk you through building a single page web application that has a customised Backbone.sync implementation.
"Get your truth out of the DOM". - Jeremy Ashkenas (Creator of Backbone.js) The solution, as the creator of Backbone.js, Jeremy Ashkenas, so frequently advocates is to stop tying your data to the DOM. Getting to Know Backbone.js - Tuts+ Code Tutorials. Welcome to part three of our series that focuses on building applications using Backbone.
If you haven't read parts one and two, I strongly recommend that you do -- just so you know where we're at and what we've covered so far. In part one, we took a basic look and models, views and collections. In part two, we looked at routers, events and the history modules. Backbone.js Application Walkthrough Part 1: HTML and Models - Video Tutorial. The day everyone has long been waiting for has finally arrived.
Pull requests and comments always welcome. Prelude Not so long ago, “data-rich web application” was an oxymoron. Today, these applications are everywhere and you need to know how to build them. Traditionally, web applications left the heavy-lifting of data to servers that pushed HTML to the browser in complete page loads. Think of the Ajax shopping cart which doesn’t require a refresh on the page when adding an item to your basket.
I wrote a guide for internal use that documents those best practices (much of it based on shorter blog posts here), and I've snapshotted it here on my blog to benefit other engineering teams using Backbone and to give potential Coursera engineers an idea of the current stack. This was snapshotted on July 24th, 2013, so please keep in mind that the Coursera frontend stack may change over time as the team figures out new and better ways to do things. If you're interested in joining Coursera, check out the many job listings here. The frontend team is a really smart and fun bunch, and there are a lot of interesting technical and usability challenges in the future.
The Architecture This approach has several advantages, atleast as compared to a traditional data-rendered-into-HTML approach: The APIs Request: Response: Building Large Backbone Applications. Backbone gives structure to web applications, but often it is not enough.
A lot of questions arise when complexity grows. How do we manage UI interactions? What do we do with domain use cases? What about client/server interactions? Finally, how do we wire everything up? Code School - Anatomy of Backbone. Backbone.js Tutorial - Beginners.