| My normal setup... (many cake sites from one cake install) | |
| -------------------------------------------------------------------------------- | |
| sudo apt-get install php5-dev mysql-server apache2|cherokee etc | |
| cd /var/www | |
| mkdir frameworks | |
| cd frameworks | |
| git clone git://github.com/cakephp/cakephp.git cakephp/ |
| #!/bin/bash | |
| # which cake version that will be bundled in the zip file | |
| CAKE_13_STABLE=1.3.15 | |
| CAKE_21_STABLE=2.1.4 | |
| CAKE_23_LATEST=2.3.0-RC1 | |
| # location of working repositories | |
| CAKE_REPO=~/work/core/cake_2.0/ | |
| CROOGO_REPO=~/work/personal/deploy/croogo/ |
Locate the section for your github remote in the .git/config file. It looks like this:
[remote "origin"]
fetch = +refs/heads/*:refs/remotes/origin/*
url = git@github.com:joyent/node.git
Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:
| var GreedyMesh = (function greedyLoader() { | |
| // contains all forward faces (in terms of scan direction) | |
| var mask = new Int32Array(4096); | |
| // and all backwards faces. needed when there are two transparent blocks | |
| // next to each other. | |
| var invMask = new Int32Array(4096); | |
| // setting 16th bit if transparent | |
| var kTransparentMask = 0x8000; |
major goal: "everything is just an object and voxel-engine just deals with keeping a list of objects for collisions" via voxel-chunks
pending:
voxels.createChunkRadiusStream().pipe(voxels.generateChunkStream()).pipe(game.voxels) for async chunk loadinginvestigated/completed:
This is a short guide that will teach you the workflows that have been figured out by the voxel.js community for writing node modules + sharing them on NPM and Github. It is assumed that you have a basic understanding of JavaScript, github and the command line (if not you can check out an introduction to git and the command line or learn JS basics from JavaScript for Cats)
The voxel-tower repository on github contains all the example code from this guide.
| <html> | |
| <head> | |
| <title>spinnin' cubes! yes! plural!</title> | |
| <style>canvas { width: 100%; height: 100% }</style> | |
| </head> | |
| <body> | |
| <script src="https://raw.github.com/mrdoob/three.js/master/build/three.js"></script> | |
| <script> | |
| //create basic context | |
| var main_scene = new THREE.Scene(); |
| function run(generator) { | |
| var iterator = generator(resume); | |
| var data = null, yielded = false; | |
| iterator.next(); | |
| yielded = true; | |
| check(); | |
| function check() { | |
| while (data && yielded) { |
UPDATE working on this here!
so… I've had this weird idea recently...
In git (and in other secure + distributed systems) you have a tree of hashes where each object is identified by it's hash and objects contain pointers to other objects. They just have the hash of other objects stored inside them.
The final result: require() any module on npm in your browser console with browserify
This article is written to explain how the above gif works in the chrome (and other) browser consoles. A quick disclaimer: this whole thing is a huge hack, it shouldn't be used for anything seriously, and there are probably much better ways of accomplishing the same.
Update: There are much better ways of accomplishing the same, and the script has been updated to use a much simpler method pulling directly from browserify-cdn. See this thread for details: mathisonian/requirify#5
