insin

/** @jsx React.DOM */

var STATES = [
  'AL', 'AK', 'AS', 'AZ', 'AR', 'CA', 'CO', 'CT', 'DE', 'DC', 'FL', 'GA', 'HI',
  'ID', 'IL', 'IN', 'IA', 'KS', 'KY', 'LA', 'ME', 'MD', 'MA', 'MI', 'MN', 'MS',
  'MO', 'MT', 'NE', 'NV', 'NH', 'NJ', 'NM', 'NY', 'NC', 'ND', 'OH', 'OK', 'OR',
  'PA', 'RI', 'SC', 'SD', 'TN', 'TX', 'UT', 'VT', 'VA', 'WA', 'WV', 'WI', 'WY'
]

var Example = React.createClass({

benjamingr

So, we figured creating our own chatroom could be fun.

It's something we can all work together on.

We don't plan on moving there but the project itself could be interesting for the whole room to collaborate work on.

What we need to discuss now:

• What technologies we want to use (Node/Express seems natural for serverside. What about clientside?)
• What features to we want? Do we just want to start with a clone of the SO chat?

BonsaiDen

/**
  * Copyright (c) 2013 Ivo Wetzel.
  *
  * Permission is hereby granted, free of charge, to any person obtaining a copy
  * of this software and associated documentation files (the "Software"), to deal
  * in the Software without restriction, including without limitation the rights
  * to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
  * copies of the Software, and to permit persons to whom the Software is
  * furnished to do so, subject to the following conditions:
  *

rlemon

// ==UserScript==
// @name          GIF Mask
// @author        Robert Lemon
// @version       0.0.7.1
// @namespace     
// @description   Replaces gifs with a single frame canvas (click to watch, click to hide)
// @include       http://chat.stackexchange.com/rooms/*
// @include       http://chat.stackoverflow.com/rooms/*
// ==/UserScript==

simonsarris

http://jsperf.com/fillorpath

http://jsperf.com/single-rects

~

http://jsperf.com/distancesquared

http://jsperf.com/mozopaque

cobyism

Deploying a subfolder to GitHub Pages

Sometimes you want to have a subdirectory on the master branch be the root directory of a repository’s gh-pages branch. This is useful for things like sites developed with Yeoman, or if you have a Jekyll site contained in the master branch alongside the rest of your code.

For the sake of this example, let’s pretend the subfolder containing your site is named dist.

Step 1

Remove the dist directory from the project’s .gitignore file (it’s ignored by default by Yeoman).

rlemon

/* Rotates the page 180deg when the user hovers over the body.
   Only works for webkit browsers */
(function() {
    var s = document.createElement('style');
    s.textContent = '.trololol:hover{-webkit-transform: rotate(180deg);';
    document.head.appendChild(s);
    document.body.classList.add('trololol');
}());

gerryster

// GeoChart from https://google-developers.appspot.com/chart/interactive/docs/gallery/geochart

// Try out by pasting code into: https://code.google.com/apis/ajax/playground/?type=visualization#geo_chart

function drawVisualization() {
  var data = google.visualization.arrayToDataTable([
    ['State', 'Foo Factor'],
    ['US-IL', 200],
    ['US-IN', 300],
    ['US-IA', 20],

ralt

define(function () {
    function getAllPaths() {
        return [{
            path: "",
            url: "ui/notifications",
            callback: function (notifications) {
                notifications.init()
            }
        }, {
            path: "option=com_community&view=profile",

domenic

This article has been given a more permanent home on my blog. Also, since it was first written, the development of the Promises/A+ specification has made the original emphasis on Promises/A seem somewhat outdated.

You're Missing the Point of Promises

Promises are a software abstraction that makes working with asynchronous operations much more pleasant. In the most basic definition, your code will move from continuation-passing style:

getTweetsFor("domenic", function (err, results) {
 // the rest of your code goes here.