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.

ronkorving

(function (window) {

        // This library re-implements setTimeout, setInterval, clearTimeout, clearInterval for iOS6.
        // iOS6 suffers from a bug that kills timers that are created while a page is scrolling.
        // This library fixes that problem by recreating timers after scrolling finishes (with interval correction).
	// This code is released in the public domain. Do with it what you want, without limitations. I do not promise
	// that it works, or that I will provide support (don't sue me).
	// Author: rkorving@wizcorp.jp

        var timeouts = {};

Nopik

.navbar.navbar-fixed-top
  %ul.dropdown-menu
    %li.nav-header
      Projects
    %li.divider
    {{outlet projectNames}}
    %li.divider

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'

ghempton

Ember.js Controller Brainstorm

Currently, there are several awkward points to Ember.js controllers. Namely:

1. Passing controllers around to view's not instantiated by the routing system is hard.
2. Non-singleton controllers are very difficult to manage (e.g. #each where each view has it's own controller).
3. Sharing data between controllers is difficult.

Solution for 1 and 2: Controllers are lazily created by views

wycats

Relationship Semantics

The new relationship semantics change the current app/store/transaction/adapter APIs in several ways:

Changes to the Application API

At present, a record can be freely moved across transactions as long as it has no changes. Once a record accumulates at least one change, an application cannot move it out of its current transaction until the transaction is committed or rolled back.

borismus

/**
 * Gesture recognizer for compound multi-touch transformations.
 *
 * 1. pinch/zoom/scale gesture.
 * 2. rotate gesture.
 */

function TransformRecognizer(element) {
  // Reference positions for the start of the transformation.
  this.referencePair = null;

tomdale

View Context Changes

The rules for how Ember.js evaluates Handlebars templates have recently changed, and you may need to update your application's templates to ensure they continue working..

Template Contexts

Remember that a template is always evaluated against a context object. When you render a template, values are looked up from that object. For example:

Hello, {{firstName}} {{lastName}}!

dudleyf

APPNAME = 'wh'

require 'json'
require 'rake-pipeline-web-filters'

WebFilters = Rake::Pipeline::Web::Filters

class LoaderFilter < WebFilters::MinispadeFilter
  def generate_output(inputs, output)
    inputs.each do |input|

btoone

Introduction

An introduction to curl using GitHub's API.

The Basics

Makes a basic GET request to the specifed URI

curl https://api.github.com/users/caspyin