Donald Zhan dz1984

#Four Ways To Do Pub/Sub With jQuery and jQuery UI (in the future)

Between jQuery 1.7 and some of work going into future versions of jQuery UI, there are a ton of hot new ways for you to get your publish/subscribe on. Here are just four of them, three of which are new.

(PS: If you're unfamiliar with pub/sub, read the guide to it that Julian Aubourg and I wrote here http://msdn.microsoft.com/en-us/scriptjunkie/hh201955.aspx)

##Option 1: Using jQuery 1.7's $.Callbacks() feature:

$.Callbacks are a multi-purpose callbacks list object which can be used as a base layer to build new functionality including simple publish/subscribe systems. We haven't yet released the API documentation for this feature just yet, but for more information on it (including lots of examples), see my post on $.Callbacks() here:

This idea:

Use gist to share ideas

My Ideas:

Couch Apps

Git 简要教程

##引言

鉴于使用Git有一点点门槛（比SVN稍微高一点），我写了个实用教程，如果想更进一步了解Git，或者觉得我写的太懶，推荐参考书 Progit，这本书是开源的，前四章就足够用了。

组内我和晓天、汤韬都会使用git，有问题可以线下直接问。

至于为什么要用Git，其实用SVN也是挺好的，但是SVN是集中式提交，同一时刻只能有一个人修改一个文件，这个在很多时候会比较蛋疼，另一方面SVN提交时要求联网，这样碰上断网什么的话SVN就废了。

I'm doing some research on how companies use GitHub Enterprise (or public GitHub) internally. If you can help out by answering a few questions, I'd greatly appreciate it.

What is the primary setup? Is there an organization and each official repo is owned by that organization?
Does every engineer have a fork of each repo they're working on?
Are engineers allowed to push directly to the official repo? Or must all commits go through a pull request?
Do engineers work on feature branches on the main repo or on their own forks?
Do you require engineers to squash commits and rebase before merging?
Overall, what is the workflow for getting a new commit into the main repository?
What sort of hooks do you make use of?
Are there any ops issues you encountered? (Scaling, unforeseen downtime, etc.)

Github 發 Pull Request & 貢獻流程速查

前言

此文目標讀者需先自行學會

開 Github 帳號
會 fork 程式 repository
會在自己的電腦使用命令列 git
會 clone 自己的 repository

	<?php

	/*
	* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
	* "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
	* LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
	* A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
	* OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
	* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
	* LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,

	/* The API controller
	Exports 3 methods:
	* post - Creates a new thread
	* list - Returns a list of threads
	* show - Displays a thread and its posts
	*/


	var Thread = require('../models/thread.js');
	var Post = require('../models/post.js');

	<?PHP

	# JSONP "callback" param explanation, via basic PHP script.
	#
	# "Cowboy" Ben Alman
	# http://benalman.com/

	# Set $data to something that will be serialized into JSON. You'll undoubtedly
	# have your own code for this.
	$data = array("some_key" => "some_value");

	var application_root = __dirname,
	express = require("express"),
	path = require("path"),
	mongoose = require('mongoose');

	var app = express.createServer();

	// database

	mongoose.connect('mongodb://localhost/ecomm_database');

	import numpy as np
	import warnings

	from itertools import cycle, izip

	from sklearn.utils import gen_even_slices
	from sklearn.utils import shuffle
	from sklearn.base import BaseEstimator
	from sklearn.base import ClassifierMixin
	from sklearn.preprocessing import LabelBinarizer