Backbone.js入门与实战指南(2013年版)

5星 · 超过95%的资源需积分: 9 165 浏览量更新于2024-07-23 1 收藏 6MB PDF 举报

"Apress.Beginning.Backbone.js.Dec.2013"是一本专门介绍Backbone.js的入门书籍，由Apress出版于2013年12月。该书旨在帮助读者理解和掌握这个强大的前端JavaScript框架，以便构建结构良好且高效的Web应用程序。在书中，作者首先引导读者通过一个简明的介绍，了解Backbone.js的基本概念和核心组件，包括Model（模型）、Collection（集合）和View（视图）。第一章详细阐述了Backbone.js的基础架构，强调其如何将MV*（Model-View-Controller）设计模式应用到前端开发中，帮助开发者实现模块化和数据驱动的页面设计。第二章至第四章深入剖析了Backbone.js的核心对象，如Object-Oriented编程技巧、如何创建和管理Model和Collection，以及如何使用View进行界面展示和模板技术。这些章节不仅介绍了理论知识，还提供了实际操作步骤，使读者能快速上手。第五章讨论了Router（路由器）和事件系统，如何通过定义路由规则和处理用户交互来控制应用的导航流程。第六章则通过一个完整的应用实例，展示了从头到尾如何运用所学知识构建实际项目。后续章节扩展到Backbone.js生态系统，涵盖了测试、构建过程自动化（如Grunt工具的使用）以及Backbone.js与其他库（如Marionette和Thorax）的集成。这些内容确保读者能够利用最佳实践提升开发效率和代码质量。最后，书中还包含了对编写可维护的JavaScript代码基础的讨论，以及索引，便于读者查找和回顾各个主题。这本《Apress.Beginning.Backbone.js》是一本实用的指南，适合初学者和有一定经验的JavaScript开发者，无论是在学习Backbone.js的基础用法，还是寻求进阶策略和最佳实践，都能从中受益匪浅。通过本书，读者可以系统地理解并掌握如何利用Backbone.js构建高效、可扩展的Web应用。

Chapter 1 ■ an IntroduCtIon to BaCkBone.js

Meanwhile, the model and application are created in JavaScript.

App = Ember.Application.create();

App.Person = Ember.Object.extend({

name: null,

});

App.IndexRoute = Ember.Route.extend({

model: function() {

var people = [

App.Person.create({

name: "James"

}),

App.Person.create({

firstName: "Sarah"

})

];

return people;

}

});

The amount of JavaScript code required in Ember is similar to that in Backbone. But again, Backbone’s strength is

in the dedicated model object.

Summary

What you will have noticed here is that most other frameworks provide some built-in functionality to update the view

when the model changes. Backbone is often considered a lower-level framework because all of this work has to be

accomplished by the programmer using additional code. Some may see this as a negative, but it results in a more

transparent view into how your application is actually working behind the scenes. Because you write the UI update

code yourself, it is easier to debug when there are issues. This level of control is one of the most widely quoted reasons

for developers using Backbone.

Also, as one of the more mature frameworks available, Backbone has a richer set of documentation, tutorials, and

examples across the Internet.

Backbone Adoption in the Real World

While debating whether Backbone is right for your project, it can be useful to see which other industry leaders have

adopted the technology in real-world applications used every day. This section of the book lists some high-profile

examples and gives five good reasons to use Backbone, along with another list that describes where it might not

be suitable.

Companies Using Backbone

Some of the brightest companies in the world use Backbone to power their latest applications. Let’s take a look at

three of these companies and find out why they have chosen Backbone. You’ll find many more case studies listed at

the official Backbone web site.

Chapter 1 ■ an IntroduCtIon to BaCkBone.js

Find out more at the Foursquare engineering blog, found at

http://engineering.foursquare.com/2011/12/08/web-sites-are-clients-too/.

Five Reasons to Use Backbone in Your Project

In case you’re still not convinced that Backbone is the right choice for your project, here are the five top reasons to

consider using it.

• Backbone is a library, not a framework: There’s a subtle difference between libraries and

frameworks. Frameworks are very prescriptive about how they are used in your project and

usually impose a certain style of coding that might not suit. As you saw in the section comparing

different MV* options, Backbone is the option that leaves you with the most freedom, and it can

be refactored into any existing JavaScript application without having to overhaul the app in order

to utilize the library. Backbone can be extended if you require additional functionality. You can

use any templating library alongside Backbone, so if Underscore doesn’t meet your needs or you

are familiar with something like Handlebars, you can use that instead. Because there is no two-

way data binding in Backbone by default, you won’t hit any surprise performance issues. The

library’s simplicity insulates you from such problems.

• JavaScript applications need structure: If you want to create commercial-quality JavaScript

applications, you need to impose some type of structure. Backbone’s MV* approach suits

almost every type of application, helping separate code that deals with the data model and

the view. Most client-side applications will deal with a RESTful API, and this is one of the

areas that Backbone excels at, providing synchronization functions in your model that will

implement all create, update, and delete REST calls for that data object. Using a framework

like Backbone brings a common, well-defined approach to JavaScript development that the

entire project team can easily follow. The best practices that Backbone encourages are easy to

maintain.

Figure 1-10. Foursquare desktop web site

Chapter 1 ■ an IntroduCtIon to BaCkBone.js

• Rich documentation and a large user community: Using any new technology can be daunting,

but a mature documentation set and a large community base can help take the sting out

of this. With Backbone you get this in abundance. The documentation available at

http://backbonejs.org is simple to follow, with annotated source code and examples

that help you understand every aspect of the library. Pair this with the numerous blogs and

tutorials that you will find across the Internet and you know that you’re not alone. There are a

huge number of plug-ins and extensions available for Backbone that have been created by the

user community. It’s likely that if you encounter an issue, someone has already found a way to

resolve it. We’ll take a closer look at Backbone plug-ins and extensions later in this book.

• It scales well, and credible companies are using it: In the previous section we saw just a few

big-name companies that use Backbone. But if you go to http://backbonejs.org, you will

see that there are a huge list of companies that have adopted Backbone. The library is not just

being used for experimental projects; in the case of Airbnb, Backbone proved to be such a

good solution that it is now using it on the server side. This proves that it’s a library that scales

well and that it can integrate well with any other JavaScript library, even Node.js. The maturity

of the library counts for a lot, and because Backbone has been around for almost three years

and has reached version 1.0.0, it has the edge on a lot of other MV* solutions.

• Your code base is a jQuery mess: Backbone isn’t just for fresh projects. It’s likely that you have

some legacy applications that could use some cleanup. You may have been using jQuery

extensively, manipulating the DOM manually and making $.ajax calls. If this is the case,

Backbone can be the perfect replacement, with the Backbone.Model object enabling you

to use simpler code to achieve the same results. Don’t forget that you don’t need to use

absolutely everything that Backbone provides. You can pick and choose what suits your

application at the time.

Three Reasons Backbone Might Not Be Right for You

In some cases using Backbone might not make sense for your application. Using the wrong library for any project can

have devastating consequences. This list shows when Backbone is not such a good idea:

• Proof-of-concept applications: Sometimes you just want to get a quick experiment together

to prove what a particular user interface could look like. If you’re creating something really

simple, it’s likely that Backbone would be too much and that you might get something

together faster by using something like AngularJS. If you’re not already up to speed with how

Backbone works, some other solutions bring you from zero to app in less time. However, if the

proof of concept turns into a real application, it is worth considering Backbone for the real

implementation.

• You’re not comfortable with lower-level JavaScript: As one of the less opinionated MV*

solutions, Backbone leaves a lot of work for the developer to do. The two-way data binding

between model and view is one of these tasks. While a lot of the development community

is happy to write the code for this binding, some may find it a daunting. More opinionated

frameworks that give more guidance into the implementation details of the entire application

can be useful, but beware of potential performance issues.

• You are creating a small web page: Backbone is suitable for developers who are creating web

applications, not just trivial web pages. There is no doubt that Backbone would be overkill for

something that simple.

剩余287页未读，继续阅读

heilee88

粉丝: 0
资源: 58

Backbone.js入门与实战指南(2013年版)

BackboneJS教程（全套教程 超清版）

Apress.Beginning.Arduino.Dec.2010

Apress.Beginning.CouchDB.Dec.2009.pdf

Apress.Beginning.FSharp.Dec.2009.rar

Apress.Beginning.jQuery.Feb.2013

Apress.Beginning.C.Sharp.2005.Databases.From.Novice.to.Professional.Dec.2006

Apress.Beginning.Java.EE.7.2013

Apress.Beginning.EJB.3.2nd.Edition.May.2013.rar

Apress.Beginning Oracle SQL.Dec 2009

Apress.Beginning.Android.C++.Game.Development.2013

最新资源

BackboneJS教程（全套教程超清版）