building web apps with ember .js

Building Web Apps with Ember.js

ISBN: 978-1-449-37092-3

US $29.99 CAN $31.99

Twitter: @oreillymedia

facebook.com/oreilly

If you’re a web developer interested in building scalable single-page

applications—full-stack, browser-based apps that connect to a backend—

this practical guide shows you how to use Ember.js, the popular JavaScript

framework based on the model-view-controller (MVC) architectural pattern.

Through the course of the book, you’ll learn how to build a prototype

Ember application (a musician index called Rock’n’Roll Call), using routers,

templates, models, controllers, and views. You’ll also understand how

Ember’s convention over configuration approach helps you persist data,

build backend technologies, and create widgets for developing production￾capable applications that behave like desktop software.

■ Set up workflow management and boilerplate code creation

■ Learn how Ember’s “developer ergonomics” help you use

less code

■ Write templates for the book’s prototype with Handlebars.js

■ Use routers to manage application states without reloading

the page

■ Connect controllers and views with events, and sync data with

data-binding

■ Build an Ember backend with a RESTful API or Ruby on Rails

■ Use the Ember Data library to persist data and talk to the

backend

■ Write reusable encapsulated widgets to extend your applications

Jesse Cravens, a principal web engineer at frog design, works with leading

companies to design, engineer, and bring meaningful products and services to

market. Jesse is currently focused on single-page web applications, the mobile

web, and HTML5.

Thomas Q Brady, Technology Director at Reaction, Inc., has built back-office

software, business simulations, interactive marketing, high-fidelity prototype

hardware and software, Arduino-powered bluetooth caller ID watches, and web

applications for clients and for fun.

Jesse Cravens & Thomas Q Brady

Building

Web Apps with

Ember.js

WRITE AMBITIOUS JAVASCRIPT

JAVASCRIPT

Building Web Apps with Ember.js & Brady Cravens

www.it-ebooks.info

Building Web Apps with Ember.js

ISBN: 978-1-449-37092-3

US $29.99 CAN $31.99

Twitter: @oreillymedia

facebook.com/oreilly

If you’re a web developer interested in building scalable single-page

applications—full-stack, browser-based apps that connect to a backend—

this practical guide shows you how to use Ember.js, the popular JavaScript

framework based on the model-view-controller (MVC) architectural pattern.

Through the course of the book, you’ll learn how to build a prototype

Ember application (a musician index called Rock’n’Roll Call), using routers,

templates, models, controllers, and views. You’ll also understand how

Ember’s convention over configuration approach helps you persist data,

build backend technologies, and create widgets for developing production￾capable applications that behave like desktop software.

■ Set up workflow management and boilerplate code creation

■ Learn how Ember’s “developer ergonomics” help you use

less code

■ Write templates for the book’s prototype with Handlebars.js

■ Use routers to manage application states without reloading

the page

■ Connect controllers and views with events, and sync data with

data-binding

■ Build an Ember backend with a RESTful API or Ruby on Rails

■ Use the Ember Data library to persist data and talk to the

backend

■ Write reusable encapsulated widgets to extend your applications

Jesse Cravens, a principal web engineer at frog design, works with leading

companies to design, engineer, and bring meaningful products and services to

market. Jesse is currently focused on single-page web applications, the mobile

web, and HTML5.

Thomas Q Brady, Technology Director at Reaction, Inc., has built back-office

software, business simulations, interactive marketing, high-fidelity prototype

hardware and software, Arduino-powered bluetooth caller ID watches, and web

applications for clients and for fun.

Jesse Cravens & Thomas Q Brady

Building

Web Apps with

Ember.js

WRITE AMBITIOUS JAVASCRIPT

JAVASCRIPT

Building Web Apps with Ember.js & Brady Cravens

www.it-ebooks.info

Jesse Cravens and €omas Q Brady

Building Web Apps with

Ember.js

www.it-ebooks.info

978-1-449-37092-3

[LSI]

Building Web Apps with Ember.js

by Jesse Cravens and Thomas Q Brady

Copyright © 2014 Jesse Cravens and Thomas Q Brady. All rights reserved.

Printed in the United States of America.

Published by O’Reilly Media, Inc. , 1005 Gravenstein Highway North, Sebastopol, CA 95472.

O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are

also available for most titles (http://my.safaribooksonline.com). For more information, contact our corpo‐

rate/institutional sales department: 800-998-9938 or [email protected].

Editors: Simon St. Laurent and Brian MacDonald

Production Editor: Kara Ebrahim

Copyeditor: Jasmine Kwityn

Proofreader: Amanda Kersey

Indexer: Judy McConville

Interior Designer: David Futato

Cover Designer: Ellie Volckhausen

Illustrator: Rebecca Demarest

July 2014: First Edition

Revision History for the First Edition

2014-07-07: First Release

See http://oreilly.com/catalog/errata.csp?isbn=9781449370923 for release details.

Nutshell Handbook, the Nutshell Handbook logo, and the O’Reilly logo are registered trademarks of

O’Reilly Media, Inc. Building Web Apps with Ember.js, the image of a wood dormouse, and related trade

dress are trademarks of O’Reilly Media, Inc.

Many of the designations used by manufacturers and sellers to distinguish their products are claimed as

trademarks. Where those designations appear in this book, and O’Reilly Media, Inc., was aware of a trade‐

mark claim, the designations have been printed in caps or initial caps.

While every precaution has been taken in the preparation of this book, the publisher and authors assume

no responsibility for errors or omissions, or for damages resulting from the use of the information con‐

tained herein.

www.it-ebooks.info

Table of Contents

Preface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

1. Introducing Ember.js and Ambitious Web Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

What Is an “Ambitious Web Application”? 1

Ambitious Web Applications Are Not Documents 2

Ambitious Web Applications Are Stateful 2

Ambitious Web Applications Are Long-Lived 4

Ambitious Web Applications Have Architecture 5

What Is Ember.js? 7

Why Choose Ember? 7

Developer Ergonomics? 8

What’s an ORM? 8

What Is Ruby on Rails? 9

What Is Node.js? 9

Express.js 9

2. The Basics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Hello, World Wide Web 11

SimpleHTTPServer: Just Like It Says on the Tin 13

Data Binding 15

But Where’s All the Code? 16

Uh, What’s a Router? 17

Ember in Action 18

Wrapping Things Up 21

3. Ember Boilerplate and Work€ow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Git 25

What Is Yeoman? 26

iii

www.it-ebooks.info

Installing Yeoman 26

Using Yo’s Ember Application Generator 27

Installing Dependencies 27

Install the Generator 28

Running the Generator 29

Using Bower 33

Grunt 34

Build, Run, Test 35

Debugging with the Ember Inspector for Chrome and Firefox 38

Wrapping Things Up 43

4. Building the RocknRollCall Prototype: Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Rock ‘n’ Roll 45

Starting with HTML 47

The Basics of Handlebars.js 48

Variables 51

Linking with the {{link-to}} Helper 52

Input with the {{input}} Helper 53

Lists with the {{each}} Helper 56

Conditionals with the {{if}} and {{else}} Helpers 58

Capturing User Interaction with the {{action}} Helper 59

Bound Attributes 60

Creating Custom Helpers 62

Wrapping Things Up 65

5. Building the RocknRollCall Prototype: The Router, Routes, and Models. . . . . . . . . . . . . 67

URLs : The Web :: “Saved Game Passwords” : The Nintendo Entertainment

System 68

Routing 69

The Router 71

Dynamic Routes 75

Routes 76

Models 78

Promises, Promises 80

The model() Method 81

Wrapping Things Up 83

6. Building the RocknRollCall Prototype: Controllers, Views, Data Binding, and Events. . 85

Controllers 85

Computed Properties 89

The Power of Promises and the model Method 90

Views 97

iv | Table of Contents

www.it-ebooks.info

Wrapping Things Up 98

7. Persisting Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Not Rolling Our Own Ajax 99

There Must Be a Better Way 102

Ember Client-Side Persistence Libraries 102

Ember Data 102

Ember Model 102

Ember Restless 103

Ember Persistence Foundation 103

An Ember Data Deep Dive 103

Setting Up the Router and Activity View for the Activity State 103

Models 104

Persisting Records Based on User Interaction 106

Abstraction Layers: Store, Serializers, and Adapters 109

Ember Data Store 109

Serializer 110

Adapters 111

Wrapping Things Up 115

8. Building an Ember Backend. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

RESTful Web Service APIs 118

Ember Data RESTAdapter 118

EAK (Ember App Kit) API Stubs with Express 118

Why Use Rails? 123

Managing Dependencies with RVM (Ruby Version Manager) and Bundler 123

Installing Rails 124

Generating the Initial Application 124

Updating the Gemfile 125

Removing TurboLinks 126

Understanding Rails MVC and the Single-Page Application 127

Running Tests 129

Adding Ember 130

Wrapping Things Up 136

9. Ember Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

The Anatomy of an Ember Component 138

Create a Template 138

Extending Ember.Component 140

Building a Heat Map Visualization with D3 141

Table of Contents | v

www.it-ebooks.info

Wrapping Things Up 145

10. Ember Testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Ember Testing with Ember App Kit, Qunit, and Testem 148

Testem and QUnit Test Runners 150

Ember Client-Side Integration Testing 152

Helpers 153

Testing the Index Page 153

Testing the Activities Route 155

Ember Unit Testing 158

Using Ember-Qunit 160

Unit Testing Routes 161

Using Fixtures 162

Unit Testing Models 164

Wrapping Things Up 164

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

vi | Table of Contents

www.it-ebooks.info

Preface

Building Web Apps with Ember.js

Welcome to Building Web Apps with Ember.js! This book is largely about building

production-capable, browser-based appplicatons. Some might call these single-page

apps while others say HTML5 apps, client MVC apps, or rich Internet apps; but in the

end, these types of applications are one and the same: the web browser is the applica‐

tion platform, and the server provides remote service endpoints. After years of writ‐

ing and using many of the solutions available to manage complex applications of this

type, we have settled on Ember.js as our primary toolset. In this book, we will attempt

to both teach you what we know about Ember, and, along the way, demonstrate for

you why it has become our primary toolset for building web applications.

In 2005, I (Jesse) discovered JavaScript and the XMLHttpRequest object while working

at a digital agency that deployed .NET and Drupal applications with rich, Flash and

web frontends. At the time, JavaScript was a disrespected “toy” language used to

sprinkle functionality onto the top of traditional web applications. Ironically, much of

the JavaScript work I did then involved using flashvars to create a bridge between

PHP and browser-based Flash applications.

But, at the time, Flash frontends were a necessary evil. Browsers were largely incapa‐

ble of supporting rich, interactive experiences, and respectable JavaScript libraries

like MooTools, YUI, and Dojo were only beginning to mature.

As I began taking additional risks by using more and more JavaScript in my applica‐

tions, I started to find other like-minded developers that also believed that browsers

would evolve and that JavaScript was more than just a toy language. We believed Java‐

Script was a full-featured, object-oriented, professional language that was capable of

being used to build high-performing production applications. A strong community

began to evolve, fueled largely by pioneers like Douglass Crockford, John Resig, Paul

Irish, and Christian Heilmann to name a few, and eventually frontend developer be‐

came a professional job class in many organizations.

vii

www.it-ebooks.info

In 2007, I took my JavaScript skills to the enterprise. I was hired to begin building a

complex, rich Internet application within an enterprise J2EE stack. This introduced

me to many of the most common challenges presented by large-scale development:

lack of JavaScript and frontend expertise, server-centric web legacy, complex cross￾browser and mobile-web fragmentation compatibility requirements, and lack of pro‐

visioned desktop and development tooling for frontend developers, just to name a

few. Being faced with all these limitations was some of the most challenging work of

my career—not to mention overcoming the naysayers that didn’t want to see the end

of safe, traditional web applications.

Over the next couple of years, I focused solely on implementing and deploying a sol‐

ution that was in many ways before its time. Many of the tools that are available today

were nascent, or nonexistent at the time, including client MV* libraries, client-side

routing and object relational mappers (ORMs), JavaScript templates, JavaScript

promises, async flow control libraries, and web components. Nevertheless, my team

and I dreamed up and implemented custom solutions within the parameters of the

project timelines and requirements. Overall it was a success, and our client MVC

framework still remains in production today.

Since 2009, I have worked on numerous applications using Backbone, Angular, and

Ember. But today, I often recommend Ember.js to the clients I work with. This is pri‐

marily due to the fact that the conventions support well-known web application de‐

velopment patterns that I have custom written or pieced together from multiple open

source libraries. Here, are the high level concepts that, in my opinion, make Ember so

valuable:

• Ember’s object model supports a classic and well understood, object-oriented

pattern of class inheritance through extend, object initialization, getters and set‐

ters, and class monkey patching.

• Ember models, controllers, and components extend the Object class, which en‐

sures that these objects inherit Ember’s powerful default data binding.

• The router supports complex nesting for URL-driven applications that manage

application state in a conventional way that can be understood by those with

web-server-routing backgrounds.

• Recently, build, workflow, and testing tools in Ember have matured and become

intuitive.

• Ember’s only dependencies are on jQuery and Handlebars.js, two very well￾known and documented libraries.

• Finally, the community is vibrant, passionate, and extremely active.

In late 2012 and 2013, Thomas Brady and I found ourselves working on numerous

ambitious web UIs in our work at frog design. Despite the nascency of the framework

viii | Preface

www.it-ebooks.info

at the time, we felt Ember was the right tool for the job. We believed in the direction

the framework was heading and in the community of talented developers behind it.

At times it was frustrating, but in the end, I find myself saying all the time, “Can you

imagine what it would take to do this in another framework?”

More Than Just “Getting Started”

If you are picking up this book, we assume you have interest in building full-stack,

single-page applications. In other words, we assume that you would not only like to

architect and build a fully functional, browser-based application, but also connect it

to a backend. That being said, this book covers all aspects of building applications

with Ember. So, in addition to providing you with a complete overview of the HTML

and JavaScript necessary to write on the frontend, we also include an implicit project

timeline via the structure and order of the chapters, development workflow and tool‐

ing, and example backend technologies that help with getting the remotely persisted

data in a format that Ember and Ember Data can easily work with.

You may be asking why we are covering all these aspects of Ember.js development.

Why not just build a frontend Ember app?

Well, before we lose you, rest assured we will cover all the basics you need in Chap‐

ter 1 and Chapter 2. The approach we take in the remainder of the book will hopeful‐

ly provide more value and context. We feel there are numerous example applications

that already provide the necessary beginner information. These applications are very

valuable, as they provide the basics and are fantastic starting points. But when you try

to meet the needs of a more complex application within the context of delivering a

production product, many development teams get stuck not knowing where to start,

which tools to use in development, and which backend technologies should be chos‐

en to persist data.

Navigating This Book

So, first and foremost, the demo application we will develop throughout the book in‐

tentionally covers many of the areas of development not included in most of the get‐

ting started applications. We also try to do this without creating an application that is

too complicated so that we don’t lose the beginner or the developer that hasn’t yet

been exposed to single-page application development in general.

Throughout the book, we provide sidebars for some of the more challenging and less

documented aspects of Ember development, such as application initializers, active

generation, promises, and debugging.

Preface | ix

www.it-ebooks.info

Establishing a pro workflow for your project can be a decision nightmare. Early on in

Chapter 3, we get this out of the way and cover most of the major tooling options so

that you’ll have a head start in getting you and your team set up for success.

In Chapter 4, we begin working with HTML, building templates using Handlebars.js,

and extending Handlebars to create our own Handlebars helpers. The fact that we can

begin with HTML is an important nuance to Ember development that works well

within a project workflow that makes minimizing duplication of efforts a high

priority.

Then in Chapter 5, we dive into the router, and begin to structure the various states of

our application and reflect those states in our URLs. Again, the fact that we are doing

this now is an important aspect to take notice of. We are prototyping, but our code

will very likely survive the transition to production.

Chapter 6 fills in the rest of the blanks, introducing controllers, data binding, and

views.

It is often advantageous to cache your data in client-side data stores to optimize the

application so that it makes as few round trips to the server as possible. There are a

number of client-side persistence solutions available. Chapter 7 covers models and

Ember Data, the most official data persistence solution for Ember.

It has also been our experience that getting the backend talking to the frontend,

without project churn, is one of the most difficult aspects of delivering a project. In

Chapter 8, we begin building service layers that will connect your remote persistence

layer to Ember’s client-side data store. Most importantly, we will do it in a developer￾friendly way through abstractions, known as adapters, to ensure efficient, project￾phase transitions.

Chapter 9 covers the basics of Ember components, a standardized (Web Compo‐

nents) approach to building functionality in a modular way, and also integration with

the third-party visualization library, D3.js.

And finally, we cover both integration and unit testing best practices in Chapter 10.

Conventions Used in This Book

The following typographical conventions are used in this book:

Italic

Indicates new terms, URLs, email addresses, filenames, and file extensions.

Constant width

Used for program listings, as well as within paragraphs to refer to program ele‐

ments such as variable or function names, databases, data types, environment

variables, statements, and keywords.

x | Preface

www.it-ebooks.info

Constant width bold

Shows commands or other text that should be typed literally by the user.

Constant width italic

Shows text that should be replaced with user-supplied values or by values deter‐

mined by context.

This icon signifies a tip, suggestion, or general note.

This icon indicates a warning or caution.

Using Code Examples

Supplemental material (code examples, exercises, etc.) is available for download at

https://github.com/emberjsbook.

This book is here to help you get your job done. In general, if example code is offered

with this book, you may use it in your programs and documentation. You do not

need to contact us for permission unless you’re reproducing a significant portion of

the code. For example, writing a program that uses several chunks of code from this

book does not require permission. Selling or distributing a CD-ROM of examples

from O’Reilly books does require permission. Answering a question by citing this

book and quoting example code does not require permission. Incorporating a signifi‐

cant amount of example code from this book into your product’s documentation does

require permission.

We appreciate, but do not require, attribution. An attribution usually includes the ti‐

tle, author, publisher, and ISBN. For example: “Building Web Apps with Ember.js by

Jesse Cravens and Thomas Q Brady (O’Reilly). Copyright 2014 Jesse Cravens and

Thomas Q Brady, 978-1-4493-7092-3.”

If you feel your use of code examples falls outside fair use or the permission given

above, feel free to contact us at [email protected].

Preface | xi

www.it-ebooks.info

Safari® Books Online

Safari Books Online is an on-demand digital library that delivers

expert content in both book and video form from the world’s

leading authors in technology and business.

Technology professionals, software developers, web designers, and business and crea‐

tive professionals use Safari Books Online as their primary resource for research,

problem solving, learning, and certification training.

Safari Books Online offers a range of product mixes and pricing programs for organi‐

zations, government agencies, and individuals. Subscribers have access to thousands

of books, training videos, and prepublication manuscripts in one fully searchable da‐

tabase from publishers like O’Reilly Media, Prentice Hall Professional, Addison￾Wesley Professional, Microsoft Press, Sams, Que, Peachpit Press, Focal Press, Cisco

Press, John Wiley & Sons, Syngress, Morgan Kaufmann, IBM Redbooks, Packt,

Adobe Press, FT Press, Apress, Manning, New Riders, McGraw-Hill, Jones & Bartlett,

Course Technology, and dozens more. For more information about Safari Books On‐

line, please visit us online.

How to Contact Us

Please address comments and questions concerning this book to the publisher:

O’Reilly Media, Inc.

1005 Gravenstein Highway North

Sebastopol, CA 95472

800-998-9938 (in the United States or Canada)

707-829-0515 (international or local)

707-829-0104 (fax)

We have a web page for this book, where we list errata, examples, and any additional

information. You can access this page at http://bit.ly/bwa-emberjs.

To comment or ask technical questions about this book, send email to bookques‐

[email protected].

For more information about our books, courses, conferences, and news, see our web‐

site at http://www.oreilly.com.

Find us on Facebook: http://facebook.com/oreilly

Follow us on Twitter: http://twitter.com/oreillymedia

xii | Preface

www.it-ebooks.info

Watch us on YouTube: http://www.youtube.com/oreillymedia

Acknowledgments

Many thanks for all the hard work provided by numerous individuals within the Em‐

ber community and of course, the Ember core team. The momentum and change

within the community has created enormous challenges in building projects for cli‐

ents and keeping the information in this book up to date. But it is all worth it when

an API becomes more intuitive or a new feature is merged into core. Thanks for re‐

sponding to our stack overflows and IRC questions and supporting the creation of

this book.

Special thanks to all of our reviewers and editors at O’Reilly, and to technical reviewer

Adam Luikart.

And finally, thanks to our wives and families for supporting us throughout the au‐

thoring process.

Preface | xiii

www.it-ebooks.info