Ember on Rails - Convention over Configuration on both sides of the tubes
summary
Builds a real web app with Ember.js on the client and Rails on the backend, uses Ember Data and the Chrome Ember Inspector, demonstrates two-way data binding and computed properties plus router-driven state, and proves a feature—a Twitter-like Twitter client that filters retweets—works in production. The retweet filter requires six lines of code plus a checkbox binding. Notes Ember 1.0 stability, adapter-based model fetching from Rails, and that routes set up controllers and long‑lived client objects.
AI-written summary · about
chapters (8)
- 0:00Start
- 5:05Aim of the talk
- 7:58Components
- 9:26As opposed to server- side MVC ...
- 12:31Two-way data bindings
- 13:22Computed properties
- 14:02Single source of truth
- 16:17Separation of concerns
related talks
31mEmber on Rails: #REALTALK
22mUsing Ember to Make the Seemingly Impossible Easy
22mUsing Ember to Make the Seemingly Impossible Easy
34mA Rail's Developers Intro to Ember
21mHow I Learned to Love Ember
26mModern Javascript Frameworks - Introduction to Ember.JS and Ember-CLI
39mRails and EmberCLI: an integration love story
27mDesigning for Ember Apps