zhengjia

=Navigating=
    visit('/projects')
    visit(post_comments_path(post))

=Clicking links and buttons=
    click_link('id-of-link')
    click_link('Link Text')
    click_button('Save')
    click('Link Text') # Click either a link or a button
    click('Button Value')

eric1234

UPDATE: Please see some of the forks for an updated version of this guide. I
myself have moved onto the Rails 3.1 betas to get the asset pipeline. But if
you want to stay on stable there are other folks who are keeping this guide
relevant despite the changes constantly occurring on Sprockets 2. The comments
on this gist will lead you to the right forks. :)

Some brief instructions on how to use Sprocket 2 in Rails to get CoffeeScript
powered JS and SASS powered CSS with YUI compression all via the magic of rack.

This stuff will be native in Rails 3.1 and the layout of the files on the

ppcano

var get = SC.get, set = SC.set;

PG.PhoneGapEvents = SC.Mixin.create({

  phoneGapEvents: {
      deviceready: 'deviceReady',  
      pause: 'pause',  
      resume: 'resume',  
      online: 'online',  
      offline: 'offline',  

jaredhanson

// Based off example code from Hal Robertson
// https://github.com/halrobertson/test-restify-passport-facebook
// See discussion: https://groups.google.com/forum/?fromgroups#!topic/passportjs/zCz0nXB_gao

var restify = require('restify')

// config vars
var FB_LOGIN_PATH    = '/api/facebook_login'
var FB_CALLBACK_PATH = '/api/facebook_callback'
var FB_APPID = '<<YOUR APPID HERE>>'

zenkay

Ruby, RVM and Mountain Lion

Key problems

Mountain Lion (10.8) has three main difference compared to Lion (10.7):

• XCode 4.4 does not install Command Line Tools by default
• X11 isn't available anymore
• The installed version of OpenSSL has some bugs

How to work around

charlesjolley

# example view implements a simple dragging for mouse events.
Wall.DevView = Ember.View.extend

  mouseDown: (ev) ->
    ev.dispatcher.lock @, 'mouseMove', 'mouseUp'
    @_mouseDown = @$().offset()
    @_mouseDown.pageX = ev.pageX
    @_mouseDown.pageY = ev.pageY
    @_mouseDown.dispatcher = ev.dispatcher
    console.log 'mouseDown'

toranb

var get = Ember.get;

/**
 *   @extends Ember.Mixin
 *
 *     Implements common filter / sort / pagination behavior for array controllers
 *     */
Ember.FilterSortSliceMixin = Ember.Mixin.create({

  filterBy: '',

domenic

"use strict"

Q = require("..")

other = {} # a dummy value we don't want to be strict equal to
sentinel = {} # a sentinel fulfillment value to test for with strict equality

describe "Chaining off of a fulfilled promise", =>
    describe "when the first fulfillment callback returns a new value", =>
        it "should call the second fulfillment callback with that new value", (done) =>

domenic

This article has been given a more permanent home on my blog. Also, since it was first written, the development of the Promises/A+ specification has made the original emphasis on Promises/A seem somewhat outdated.

You're Missing the Point of Promises

Promises are a software abstraction that makes working with asynchronous operations much more pleasant. In the most basic definition, your code will move from continuation-passing style:

getTweetsFor("domenic", function (err, results) {
 // the rest of your code goes here.

tomdale

WARNING

This gist is outdated! For the most up-to-date information, please see http://emberjs.com/guides/routing/!

It All Starts With Templates

An Ember application starts with its main template. Put your header, footer, and any other decorative content in application.handlebars.

<header>