From the beginning Ember was designed around several key ideas:
- More productive out of the box: Ember is one component of a set of tools that work together to provide a complete development stack. The aim of these tools is to make the developer productive immediately. For example Ember CLI, provides a standard application structure and build pipeline. It also has a plug-gable architecture and over 3500 addons to enhance and extend it.
- Stability without stagnation: This is the idea that backward compatibility is important and can be maintained while still innovating and evolving the framework.
Ember consists of five key concepts:
- In Ember, the state of an application is represented by a URL. Each URL has a corresponding route object that controls what is visible to the user.
- Every route has an associated model, containing the data associated with the current state of the application. While one can use jQuery to load JSON objects from a server and use those objects as models, most applications use a model library such as Ember Data to handle this.
- Templates are used to build the application’s HTML and are written with the HTML Bars templating language. (HTML Bars is a variation of Handlebars that builds DOM elements rather than a String.)
- Services are just singleton objects to hold long-lived data such as user sessions.
Ember also provides dependency injection, declarative two-way data binding, computed properties, and automatically-updating templates.
The above is a brief about Ember.js. Watch this space for more updates on the latest trends in Technology.