Chapter 3. Putting everything together using Ember.js Router
This chapter covers
- Comparing server-side and client-side MVC models
- Exploring the Ember.js MVC model in detail
- Enriching the Ember.js MVC model statecharts
- Binding controllers and views together
- Using the Ember Container
Ember.js attempts to put the developer into a full-featured, client-side Model-View-Controller (MVC) pattern, while also enriching the controller layer with a full-featured statechart implementation called Ember Router. If you’re unfamiliar with statecharts, don’t worry. I’ll touch on the key points of a statechart in section 3.3, and provide a link where you can read the complete specification.
Ember Router allows you to map out each of your application’s states into a hierarchical structure containing the relationship between the different states in your application as well as the paths that your user can travel through your application. Implemented correctly, these routes allow you to build a web app with a firm and stable structure with states that are loosely coupled, clearly defined, and highly testable.