bebraw

IMPORTANT! Remember to check out the wiki page at https://github.com/bebraw/jswiki/wiki/Game-Engines for the most up to date version. There's also a "notes" column in the table but it simply does not fit there... Check out the raw version to see it.

This table contains primarily HTML5 based game engines and frameworks. You might also want to check out the [[Feature Matrix|Game-Engine-Feature-Matrix]], [[Game Resources]] and [[Scene Graphs]].

Name	Size (KB)	License	Type	Unit Tests	Docs	Repository	Notes
Akihabara	453	GPL2, MIT	Classic Repro	no	API	github	Intended for making classic arcade-style games in JS+HTML5
AllBinary Platform	Platform Dependent	AllBinary	2D/2.5D/3D	n

porras

Why Steak (over Cucumber)

From here

• Plain text have no value if people writing and reading the specs are developers. Code is natural language for developers (specially if that code is Ruby). Having a client who reads the specs is a possible situation and Cucumber is cool there, but in my experience that situation is not the most common one. If in your case there's no value in having your specs in English rather than in Ruby, Cucumber is an additional layer of abstraction in exchange of nothing.

• There's a myth about clients writing the specs. It sounds like a unicorn to me, but let's take it. Still, I wouldn't want it. Clients are experts in problems, I am expert in solutions. I want the client to describe the problem I have to solve, not to describe the solution.

• Some people say Cucumber is cool because you write the stories, the client validates them, and then you can start developing. That is not Agile. The on

aeden

Currently the RubyGems index is stored as a Gzip file that is a marshalled array. Whenever Bundler needs to install a gem that is not yet installed it downloads the index, gunzips it and unmarshals it. It then looks for dependencies that are described in another file that is also a gzipped and marshalled file. There are several issues that arise from this setup:

• The full index must be downloaded and parsed, but does not contain dependency data, which must then be downloaded and parsed. This is a relatively time consuming process.
• The index must be centralized.

Additionally the gems themselves are currently centralized since there is nothing in the meta data that indicates where the gem should be downloaded from. However in order to allow this it is important to find ways of keeping the index from being poisoned (is this an issue in the centralized system?)

Dependency Resolution

zaius

ctrl-z
bg

touch /tmp/stdout
touch /tmp/stderr
gdb -p $!

# In GDB
p dup2(open("/tmp/stdout", 1), 1)
p dup2(open("/tmp/stderr", 1), 2)

cowboyd

require 'v8'
require 'openssl'


class Module
  def [](name)
    self.const_get(name)
  end
end

calavera

class User
  attr_reader :name, :age
  def initialize(name, age)
    @name, @age = name, age
  end
end

class Filter
  attr_reader :method, :value
  def initialize(method, value)

protocool

/*
  As of version 1.1.2, Propane will load and execute the contents of
  ~Library/Application Support/Propane/unsupported/caveatPatchor.js
  immediately following the execution of its own enhancer.js file.

  You can use this mechanism to add your own customizations to Campfire
  in Propane.

  Below you'll find two customization examples.

craigcalef

/*
  As of version 1.1.2, Propane will load and execute the contents of
  ~Library/Application Support/Propane/unsupported/caveatPatchor.js
  immediately following the execution of its own enhancer.js file.

  You can use this mechanism to add your own customizations to Campfire
  in Propane.

  Below you'll find two customization examples.

pragdave

require File.expand_path(File.dirname(__FILE__) + '/../test_helper')

class BuildStatusTest < ActiveSupport::TestCase
  context "expiring build statii" do
    should "remove the old one" do
      assert_equal 2, BuildStatus.count
      BuildStatus.expire_old     
      statii = BuildStatus.all
      assert_equal 1, statii.size
      assert statii[0].updated_at >= 30.days.ago

dhh

require File.expand_path(File.dirname(__FILE__) + '/../test_helper')

class BuildStatusTest < ActiveSupport::TestCase
  test "remove the old statii" do
    assert_equal 2, BuildStatus.count
    BuildStatus.expire_old     
    statii = BuildStatus.all
    assert_equal 1, statii.size
    assert statii[0].updated_at >= 30.days.ago
  end