remixz

var _ = require('underscore');
var xhr = require('xhr');
var qs = require('qs');


// Throw an error when a URL is needed, and none is supplied.
var urlError = function () {
    throw new Error('A "url" property or function must be specified');
};

remixz

instructions

1. deploy server.js somewhere (i just used heroku)
2. create an API yo account on http://developer.justyo.co/, set the callback URL to http://<server url>/yo
3. run client.js on your computer (make sure you've edited the socket.io URL)
4. send yo's to your API account

notes

this is very specific to my usecase: sending a photo of me from my webcam to a group chat i have with my friends on facebook. because facebook doesn't have a chat API for group chats, i use selenium to control a browser to upload stuff. it's ugly, but it works!

remixz

Keybase proof

I hereby claim:

• I am remixz on github.
• I am zachbruggeman (https://keybase.io/zachbruggeman) on keybase.
• I have a public key whose fingerprint is C0A3 9319 C779 6547 135C C917 C985 2F5B 21CC 4407

To claim this, I am signing this object:

remixz

Spigot Changelog — Build 485 --> 617

git log --pretty=format:"* %s (EcoCityCraft/Spigot@%h | by %an on %ad)" --reverse --date=short  b864492e7a0f57b260972f9543585123ab5af79b 72123ab9a3550cfe054d8e7cb8112b2d2342766c

• Initial commit - hello future of Spigot! (EcoCityCraft/Spigot@6222297 | by md_5 on 2013-01-15)
• Update versioning check to correctly resolve api ver. (EcoCityCraft/Spigot@715955a | by md_5 on 2013-01-15)
• Fix wheat modifier potentially crashing (EcoCityCraft/Spigot@dcde41a | by md_5 on 2013-01-16)
• Re add chunk snc lock and update patch files. (EcoCityCraft/Spigot@9abbfe5 | by md_5 on 2013-01-16)

remixz

{
  "picroma": true,
  "accounts": false,
  "shop": false
}

remixz

notes

passing thoughts

• 3) Adding to the Template - in the code example, can we make those proper html comments? newbies may not know what they are, but we might as well introduce them to it now. that way, when it's properly introduced, they can think back and remember that they've seen them before.
• as i'm going through, i'm not a huge fan of the tutorial talking in the first person. would prefer second person (i.e. "if i" -> "if we"). feels... unrealistic that this person's name actually is "Drizzy Drake." 😉
• ah, there are parts written in the second person. let's make these uniform.
• (which is about 2 inches on a screen) - canadian here, what's an inch? 😉 besides my poor jokes, is this always going to be true? different DPIs will make it different lengths on a monitor. not a huge deal, but i feel like we might not need to say this. i might be looking into this too much.
• You can Google "CSS text align" to see what other alignment options are available besides center - let's dire

remixz

notes

passing thoughts

• the email to get the promo code is an autoresponder, but it looks like a person's actual email. we should make it an @hackclub.com email.
• when setting up the account, make sure to note that the credit card country is USA. for people not in USA, it defaults to their country.
• i created a phone number myself with my area code, so i didn't have to worry about any long distance charges. however, this doesn't add the dweet webhook automatically, which made the demos not work until i deleted the number i made, and then realized it was automatically provisioning a US number with the dweet webhook. i think we should add the creation of a number to the tutorial, so that they can create a number in their location and not worry about fees. basic flow
  • go to https://www.twilio.com/user/account/phone-numbers/search
  • change country to current country (if not already set)
• change the dropdown that says number to location

remixz

notes

passing thoughts

• this workshop says to sign up jsbin if i haven't already. i think this is an older workshop. we should update them all to either cloud9 or jsbin.
• inconsistency in code example. in the first step, it says the line is createCanvas(300, 500);, but the jsbin that you use is createCanvas(250, 500);. nitpick
• this is detailed. i like it. there's definitely no room for confusion so far.
• actually, one thing. where are we getting these variables like mouseX? we should note, maybe at the start, that these kind of variables aren't in every piece of code, and are part of the libraries we're using. (in this case, p5.play.js)
• on mouse movement, there's a few typos. reminder for myself to proofread.
• when in the console, we remove the ball with ball.remove(), then it says to do ball.overlap(goal);. only problem is that we never actually get the ball back! we should add a note on how to get the ball back. i hit the "run with js" button to get it back.

remixz

notes

passing thoughts

• this is just repeating the canvas explanation from the soccer tutorial. i get repetition and all that, but i think it'd just be better to link back to the first tutorial if they need a run-down of how the canvas works. we definitely should still have the part on making the canvas, and its params and all that, but i don't think we need the steps to tinker with it again.
• comp sci fundamentals! interesting. it says its unfinished, but it looks fine to me.
• "associated modules" - ??? we've never introduced the concept of modules yet, but now it's being mentioned like we know what it is. if it's unfinished, we should just leave it out. move any unfinished stuff to branches if we want to keep working on it.
• darn, the comp sci fundamentals are gone. i guess that's why it said unfinished.
• the recap says we learned what setup and draw do. but... we never actually do! at least, not until we get to the appendix after the recap, which does go in depth about how setup is called once,

remixz

additional resources

if you're looking for some new things to try with your club, try out these tutorials. some may not be as in-depth as our workshops, but for people who have done our workshops, they shouldn't be too hard. phaser is the most in-depth in terms of resources, so that'll likely be the best one to try with beginners.

phaser game engine

start with http://phaser.io/tutorials/making-your-first-phaser-game/index to learn about the engine, and then look through http://phaser.io/learn/official-tutorials and http://phaser.io/learn/community-tutorials for more tutorials and ideas for games. for even more examples, look at http://phaser.io/examples. the api documentation is here: http://phaser.io/docs first tutorial is super basic, and requires very little JS knowledge to understand. if a student's done any of the game workshops already, they're totally set.

with the first tutorial, you should create a new c9 workspace, and enter https://github.com/photonstorm/phaser.git into the clone URL box.