Bradley Priest

Building Modern Web Apps: Framework is not a four letter word 01 Dec 2012

Here are the slides from my talk at jscamp.asia about client-side MVC frameworks and EmberJS.

ed38ab removes the deprecated defaulting of a view’s context to itself, this may break some code samples around the place, but should not affect full applications.

As of PR 1393, _super() can now be called inside of computed properties.
PR 1504 adds an example of how to render a CollectionView with different childViews.
PR 1528 adds an afterRender queue for view rendering. A common use of this is to perform an action after all of a CollectionView’s children have been rendered.
PR 476 provides some initial error handling to ember-data. A 422 puts the record into an invalid state and sets an errors object onto the model. Any other server failure puts the object into an error state.
PR 422 reinstates the RESTAdapter’s default transforms.
A conscious effort is being made to be format agnostic and not hardcode any method names/fields to JSON in ember-data, see here. This shouldn’t cause too many issues unless you are using a highly customized adapter.

At the recent Ember meetup at Addepar Tom and Yehuda talked about upcoming changes to the router and ember-data, worth a look.

If I missed anything please let me know in the comments, twitter or IRC at #emberjs.

Ember 1.0.0-pre.2 has been released, now with a semver compatible release number ;)

Ember-Data revision 7 is out, which changes how relationship changes are acknowledged check out BREAKING_CHANGES for details.
A (currently) private mixin, DS.Mappable, has been introduced to implement per-type adapters, see the commit and the documentation

Explicitly missing from this post is mention of the new router API being thrown around, I don’t mean to bring personal preferences in, but I believe this is heading in the wrong direction. Currently getting started with the Ember.Router can be a bit of a hassle but I personally believe learning the philosophy behind the router/state-manager is the most important step in understanding Ember. Luckily it looks like the old API won’t be going anywhere.

If I missed anything please let me know in the comments, twitter or IRC at #emberjs.