| var _ = {}; | |
| /*********IDENTITY**********/ | |
| _.identity = function(val) { | |
| return val; | |
| }; | |
| /*********FIRST**********/ | |
| _.first = function(array, n) { |
| // assertions/compareScreenshot.js | |
| var resemble = require('resemble'), | |
| fs = require('fs'); | |
| exports.assertion = function(filename, expected) { | |
| var screenshotPath = 'test/screenshots/', | |
| baselinePath = screenshotPath + 'baseline/' + filename, | |
| resultPath = screenshotPath + 'results/' + filename, | |
| diffPath = screenshotPath + 'diffs/' + filename; |
Here is a high level overview for what you need to do to get most of an Android environment setup and maintained.
Prerequisites (for Homebrew at a minimum, lots of other tools need these too):
xcode-select --install will prompt up a dialog)Install Homebrew:
ruby -e "$(curl -fsSL https://raw.github.com/Homebrew/homebrew/go/install)"
This entire guide is based on an old version of Homebrew/Node and no longer applies. It was only ever intended to fix a specific error message which has since been fixed. I've kept it here for historical purposes, but it should no longer be used. Homebrew maintainers have fixed things and the options mentioned don't exist and won't work.
I still believe it is better to manually install npm separately since having a generic package manager maintain another package manager is a bad idea, but the instructions below don't explain how to do that.
Installing node through Homebrew can cause problems with npm for globally installed packages. To fix it quickly, use the solution below. An explanation is also included at the end of this document.
| Function.prototype.curry = function( ) { | |
| var slice = Array.prototype.slice, | |
| self = this, | |
| totalargs = self.length, | |
| partial = function( args, fn ) { | |
| return function( ) { | |
| return fn.apply( {}, args.concat( slice.call( arguments ) ) ); | |
| } | |
| }, | |
| fn = function( ) { |
One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.
Most workflows make the following compromises:
Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.
Use production SSL certificates locally. This is annoying
| var loader = new game.THREE.JSONLoader( true ) | |
| loader.load( "/horse.js", function( geometry ) { | |
| window.horseGeometry = horseGeometry = geometry | |
| }) | |
| function Horse() { | |
| this.radius = 600 | |
| this.theta = 0 | |
| this.duration = 1000 | |
| this.keyframes = 15 |
