fotinakis

(See upstream testem PR: testem/testem#819)

Since around 2012, WebKit and other browsers have throttled timers (like setTimeout) to only a max of once per second in inactive tabs.

For some test suites, this may never be an issue. But, for example, in a very large Ember test suite with >1000 acceptance tests and much custom code, it manifested as often flaky and non-deterministic test timeouts, even in headless CI environments with Chrome in xvfb.

This has caused much much testing pain that might manifest as the not-obviously-related error: Error: timeout of 10000ms exceeded. Ensure the done() callback is being called in this test.

dherman

In penance for cracking stupid jokes on Twitter, here's my Emacs cheat sheet. Emacs has a steep learning curve, so I've tried to order them by importance so you could learn them in stages.

One overall rule of thumb: pay attention to the minibuffer (the line at the bottom of the editor). It will often guide you through a process, and also gives you hints about what state you're in, such as the middle of a multi-chord sequence.

The other rule of thumb: when in doubt, C-g it out.

Basics (mandatory)

You simply can't get by without having these at your fingertips.

wycats

Recently, we've been working on extracting Ember conventions from applications we're working on into the framework. Our goal is to make it clearer how the parts of an Ember application work together, and how to organize and bootstrap your objects.

Routing

Routing is an important part of web applications. It allows your users to share the URL they see in their browser, and have the same things appear when their friends click on the link.

The Ember.js ecosystem has several great solutions for routing. But, since it is such an important part of most web applications, we've decided to build it right into the framework.

If you have already modeled your application state using Ember.StateManager, there are a few changes you'll need to make to enable routing. Once you've made those changes, you'll notice the browser's address bar spring to life as you start using your app—just by moving between states, Ember.js will update the URL automatically.

unicolet

#
# Use these commands to install sproutcore official (and development version)
# on Ubuntu linux
#
# Tested on Lucid Lynx provisioned by vagrant (http://vagrantup.com/)
# 
sudo apt-get install curl
bash -s stable < <(curl -s https://raw.github.com/wayneeseguin/rvm/master/binscripts/rvm-installer)
source /home/vagrant/.rvm/scripts/rvm
source /home/vagrant/.profile

ppcano

update:
	rm -rf packages/*; \
  cp -pr ~/Git/forks/ember.js/packages/* ./packages; \
  cp -pr ~/Git/forks/sproutcore-touch/packages/ember-touch ./packages; \
  cp -pr ~/Git/emberjs/ember-mk/packages/ember-mk ./packages

garth

var fs = require('fs')
var vm = require('vm')

var handlebarsjs = fs.readFileSync('path/to/handlebars.js', 'utf8')
var emberjs = fs.readFileSync('path/to/ember.js', 'utf8')
var templatesDir = 'path/to/template/dir'

desc('Compile all .handlebars templates')
task({ 'handlebars': [] }, function () {
  process.stdout.write('Compiling .handlebars templates')

wagenet

require 'execjs'

class HandlebarsFilter < Filter
  class << self
    def contents
      @@contents ||= [File.read("headless-ember.js"), File.read("ember.js")].join("\n")
    end

    def context
      @@context ||= ExecJS.compile(contents)

dudleyf

require "json"
class HandlebarsFilter < Rake::Pipeline::Filter
  def initialize(&block)
    block ||= proc { |input| input.sub(/\.handlebars$/, '.js') }
    super(&block)
  end

  def generate_output(inputs, output)
    inputs.each do |input|
      output.write "return Ember.Handlebars.compile(#{input.read.to_json})"

Assetfile

require "rake-pipeline-web-filters/minispade_filter"
require "rake-pipeline-web-filters/sass_compiler"
require "rake-pipeline-web-filters/ordering_concat_filter"
require "rake-pipeline-web-filters/helpers"

require "json"
class HandlebarsFilter < Rake::Pipeline::Filter
  def initialize(&block)
    block ||= proc { |input| input.sub(/\.handlebars$/, '.js') }
    super(&block)

ppcano

require('sproutcore');
require('sproutcore-touch');

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

module("Touching handlebars tests", {

  setup: function() {
    console.group(' - Setup for new test');