My jQuery Conf video is now live. Here's the skinny, video is posted below:
_that is about, as well as how to avoid some pitfalls even the experts make.
In many of my Ember routes I need to be sure that I have a populated currentUser, so I can direct users and protect certain pages appropriately. In a completely asynchronous environment like Ember, it can be hard to know when an important call has resolved. Here's my stab at a little helper (for an Ember.Route) that will make sure currentUser is available when your route's
.model() method runs.
Previously, I talked about some tips and tricks I use with Grunt.js. If you haven't heard of Grunt.js you may want to check out my article on the basics of grunt. This time I want to wrap things up by talking about custom tasks in grunt. While there are a lot of great plugins for grunt sometimes you need something custom, lucky for us grunt makes it easy for us to define our own tasks.
I want to share with you intermediate tricks for bending Grunt.js to your will, and give you an idea of how you might use them. If you don't know what Grunt is, or want a tour of the basics check our my earlier post. Otherwise read on for some grunt.js tricks.