The Basic Anatomy of an Ember Application

added by JavaScript Kicks
10/24/2014 3:27:33 PM


There are a lot of different aspects of Ember, the Javascript “framework for creating ambitious web applications,” that you’ll need to understand before you really feel a sense of mastery. But the most fundamental and useful by far is to get the basic understanding of the shape of an app. They have a few core units that you’ll want to understand, and you can mostly work out the details from there. If you’ve been a web programmer for some time, some of the anatomical units are probably pretty familiar to you. Actually most of them probably are, which is one of Ember’s best qualities. If its core architecture is familiar and comfortable to you, you can move around Ember projects simply because they’re all likely to use these same core units. But whether you’re new to each and every unit we’ll quickly summarize here, or an old hand at these concepts but new to Ember, I’m pretty sure you’ll learn something.


Bob Senoff
10/24/2014 4:10:16 PM
Ember is your favorite @benmac3

Drew Peterson
10/24/2014 6:51:45 PM
So if I understand this correctly, the relationship between the router and routes is that you declare the type of model returned by a route pattern on the router, then define a route that returns that model which will be called by the router when that pattern is hit? This is different from other MVC frameworks where that would all be one step (the definition of the route and the logic to return data). What kind of advantages do you see with that sort of separation @davidbhayes ?