creationix

define.defs = {};
define.modules = {};
function define(name, fn) {
  define.defs[name] = fn;
}
function require(name) {
  if (define.modules.hasOwnProperty(name)) return define.modules[name];
  if (define.defs.hasOwnProperty(name)) {
    var fn = define.defs[name];
    define.defs[name] = function () { throw new Error("Circular Dependency"); };

tekacs

# Usage: show <local-port> <subdomain>
function show() {
    DOMAIN=".tekacs.com"
    REMOTE="$2$DOMAIN"
    ssh -tR 1080:127.0.0.1:$1 vps "sudo ssh -Nl \$USER -L $REMOTE:80:127.0.0.1:1080 localhost"
}

maccman

class WebSocketRPC
  constructor: (host) ->
    @callbacks = {}
    @id = 0
    @socket = new WebSocket(host)
    @socket.onopen    = @onopen
    @socket.onmessage = @onmessage
    @socket.onclose   = @onclose
    
  onopen: =>

jupiterjs

The following is a VERY rough draft of an article I am working on for Alex MacCaw's @maccman's Book. It is very rough, but even now a worthwhile read. Suggestions / comments are very welcome! Please help me :-)

Introduction

JavaScriptMVC (JMVC) is an open-source jQuery-based JavaScript framework. It is nearly a comprehensive (holistic) front-end development framework, packaging utilities for testing, dependency management, documentation, and a host of useful jQuery plugins.

Yet every part of JavaScriptMVC can be used without every other part, making the library lightweight. Its Class, Model, View, and Controller combined are only 7k minified and compressed, yet even they can be used independently. JavaScriptMVC's independence lets you start small and scale to meet the challenges of the most complex applications on the web.

This chapter covers only JavaScriptMVC's $.Class, $.Model, $.View, and $.Controller. The following describes each component:

jupiterjs

TODOS:

• show .models() method and hookup

$.Controller - jQuery plugin factory

JavaScriptMVC's controllers are many things. They are a jQuery plugin factory. They can be used as a traditional view, making pagination widgets and grid controls. Or, they can be used as a traditional controller, initializing and controllers and hooking them up to models. Mostly, controller's are a really great way of organizing your application's code.

Controllers provide a number of handy features such as:

jupiterjs

$.View - Client Side Templates

JavaScriptMVC's views are really just client side templates. Client side templates take data and return a string. Typically, the strings are HTML intended to be inserted into the DOM.

$.View is a templating interface that takes care of complexities using templates:

• Convenient and uniform syntax
• Template loading from html elements or external files
• Synchronous or asynchronous template loading
• Template preloading

maccman

# Rails 3 Config
# 
# In: config/application.yml
# 
#   development:
#     github:
#       key: test
#       secret: verysecret-dev
#   production:
#     github:

arondeparon

curl -O "http://s3.amazonaws.com/bearwithclaws.baconfile.com/hackermonthly-issue0[01-19].zip"

jlong

var parser = document.createElement('a');
parser.href = "http://example.com:3000/pathname/?search=test#hash";

parser.protocol; // => "http:"
parser.hostname; // => "example.com"
parser.port;     // => "3000"
parser.pathname; // => "/pathname/"
parser.search;   // => "?search=test"
parser.hash;     // => "#hash"
parser.host;     // => "example.com:3000"

maccman

# Usage: redis-cli publish message hello

require 'sinatra'
require 'redis'

conns = []

get '/' do
  erb :index
end