Ember.JS – What it is and why we need to care about it

This is a guest post by Sourav Lahoti and his thoughts about Ember.js

Developers increasingly turn to client-side frameworks to simplify development, and there’s a big need for good ones in this area. We see a lot of players in this field, but for lots of functionality and moving parts, very few stand out in particular — Ember.js is one of them.

So what is Ember.js? Ember.js is a MVC (Model–View–Controller) JavaScript framework which is maintained by the Ember Core Team (including Tom Dale, Yehuda Katz, and others). It helps developers create ambitious single-page web applications that don’t sacrifice what makes the web great: URI semantics, RESTful architecture, and the write-once, run-anywhere trio of HTML, CSS, and JavaScript.

Why do we need to care

Ember.js is tightly coupled with the technologies that make up the web today. It doesn’t attempt to abstract that away. Ember.js brings a clean and consistent application development model. If one needs to migrate from HTML to any other technology, Ember.js framework will evolve along with the current trends in web front end technology.

It makes it very easy to create your own “component” and “template views” that are easy to understand, create and update. Coupled with its consistent way of managing bindings and computed properties, Ember.js does indeed offer much of the boilerplate code that a web framework needs.

The core concept

There are some nominal terms that you will find very common when you use ember.js and they form the basics of Ember.js:

A Route object basically represents the state of the application and corresponds to a url.
Every route has an associated Model object, containing the data associated with the current state of the application.
Controllers are used to decorate models with display logic.

A controller typically inherits from ObjectController if the template is associated with a single model record, or an ArrayController if the template is associated with a list of records.

Views are used to add sophisticated handling of user events to templates or to add reusable behavior to a template.
Components are a specialized view for creating custom elements that can be easily reused in templates.

Hands-on with Ember.js

Data Binding:

<script type=”text/x-handlebars”>
    <label>Insert your name:</label>
    {{input type=”text” value=name}}
  <p><strong>Echo: {{name}}</strong></p>
App = Ember.Application.create();

Final result when the user interacts with the web app

Ember.js does support data binding as we can see in the above example. What we type into the input is bound to name, as is the text after Echo: . When you change the text in one place, it automatically updates everywhere.

But how does this happen? Ember.js uses Handlebars for two-way data binding. Templates written in handlebars get and set data from their controller. Every time we type something in our input, the name property of our controller is updated. Then, automatically, the template is updated because the bound data changed.

A simple Visiting card demo using Handlebars

We can create our own elements by using Handlebars.


<script type="text/x-handlebars">
  {{v-card myname=name street-address=address locality=city zip=zipCode email=email}}
  <h2 class="subheader">Enter Your information:</h2>
  <label>Enter Your Name:</label>
  {{input type="text" value=name}}
  <label>Enter Your Address:</label>
  {{input type="text" value=address}}
  <label>Enter Your City:</label>
  {{input type="text" value=city}}
  <label>Enter Your Zip Code:</label>
  {{input type="text" value=zipCode}}
  <label>Enter Your Email address:</label>
  {{input type="text" value=email}}
<script type="text/x-handlebars" data-template-name="components/v-card">
  <ul class="vcard">
    <li class="myname">{{myname}}</li>
    <li class="street-address">{{street-address}}</li>
    <li class="locality">{{locality}}</li>
    <li><span class="state">{{usState}}</span>, <span class="zip">{{zip}}</span></li>
    <li class="email">{{email}}</li>


.vcard {
  border: 1px solid #dcdcdc;
  max-width: 12em;
  padding: 0.5em;
.vcard li {
  list-style: none;
.vcard .name {
  font-weight: bold;
.vcard .email {
  font-family: monospace;
label {
  display: block;
  margin-top: 0.5em;


App = Ember.Application.create();
App.ApplicationController = Ember.Controller.extend({
    name: 'Sourav',
    address: '123 M.G Road.',
    city: 'Kolkata',
    zipCode: '712248',
    email: 'me@me.com'

The component is defined by opening a new <script type="text/x-handlebars">, and setting its template name using the data-template-name attribute to be components/[NAME].

We should note that the web components specification requires the name to have a dash in it in order to separate it from existing HTML tags.

There is much more to it, I have just touched the surface. For more information, feel free to check out the Ember.js Guides.

View full post on Mozilla Hacks – the Web developer blog

Tagged on: , , ,

4 thoughts on “Ember.JS – What it is and why we need to care about it

  1. peperone

    “with a large background of strong leadership and community advocacy”, I love how modest this guy is…

Leave a Reply