Book Image

Backbone.js Blueprints

By : Andrew Burgess
Book Image

Backbone.js Blueprints

By: Andrew Burgess

Overview of this book

<p>Backbone.js is an open source, JavaScript library that helps you to build sophisticated and structured web apps. It's important to have well-organized frontend code for easy maintenance and extendability. With the Backbone framework, you'll be able to build applications that are a breeze to manage.<br /><br />In this book, you will discover how to build seven complete web applications from scratch. You'll learn how to use all the components of the Backbone framework individually, and how to use them together to create fully featured applications. In addition, you'll also learn how Backbone thinks so you can leverage it to write the most efficient frontend JavaScript code.<br /><br />Through this book, you will learn to write good server-side JavaScript to support your frontend applications. This easy-to-follow guide is packed with projects, code, and solid explanations that will give you the confidence to write your own web applications from scratch.</p>
Table of Contents (14 chapters)
Backbone.js Blueprints
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Summary


We've covered a lot in this chapter. Previously, we'd only created and read models on the server. Now, we know how to update and delete models on the server as well. This is bread-and-butter stuff for Backbone applications. Many of the apps you build will use all the four CRUD operations: creating, reading, updating, and deleting.

Another important thing to take away is the way we updated the collection by fetching from the server. You won't do it this way in every application—regularly polling the server—but the events that we listened for will be the same in every case. In fact, there's a common Backbone convention here; listen for the change event on a model and rerender the view that shows that model. Usually, you'll only need to call the render method to do that. As the main element of the view is already in the DOM, there's no need to reappend it; it will update when render is called.

Also, a notable thing in this chapter is the way we created a view class and then extended it...