jeffkreeftmeijer

.mouse, #preview{
  position: absolute;
  background-repeat: no-repeat;
  height: 22px;
  min-width: 15px;
  z-index: 100;
}

.mouse{
  background-image: url('../images/cursor.png');

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"

jonathanmoore

Share Counts

I have always struggled with getting all the various share buttons from Facebook, Twitter, Google Plus, Pinterest, etc to align correctly and to not look like a tacky explosion of buttons. Seeing a number of sites rolling their own share buttons with counts, for example The Next Web I decided to look into the various APIs on how to simply return the share count.

If you want to roll up all of these into a single jQuery plugin check out Sharrre

Many of these API calls and methods are undocumented, so anticipate that they will change in the future. Also, if you are planning on rolling these out across a site I would recommend creating a simple endpoint that periodically caches results from all of the APIs so that you are not overloading the services will requests.

Twitter

robertjwhitney

# http://stackoverflow.com/a/8936202
#
# ActiveAdmin already includes the necessary jquery in active_admin/base,
# so just add this to javascripts/active_admin.js after //= require active_admin/base
# 
# 
# Serialize and Sort 
# 
# model_name - you guessed it, the name of the model we are calling sort on.
#              This is the actual variable name, no need to change it.

proudlygeek

// http://jsfiddle.net/suBPQ/

$.ajax({
    url: "http://api_test_server.proudlygeek.c9.io/",
    success: function(data) {
        console.log(data);    
    }
});​

concerning.rb

class Module
  # We often find ourselves with a medium-sized chunk of behavior that we'd
  # like to extract, but only mix in to a single class.
  #
  # We typically choose to leave the implementation directly in the class,
  # perhaps with a comment, because the mental and visual overhead of defining
  # a module, making it a Concern, and including it is just too great.
  #
  #
  # Using comments as lightweight modularity:

HarishChaudhari

zpao

/** @jsx React.DOM */
var MyComponent = React.createClass({
  render: function() {
    // Defaults in case the props are undefined. We'll have a solution for this
    // soon that is less awkward.
    var perMinute = this.props.perMinute || '-';
    var perDay = this.props.perDay || '-';
    return (
      <div>
        <h3>Clickouts</h3>

petehunt

/** @jsx React.DOM */
var MyComponent = React.createClass({
  getInitialState: function() {
    // set up the initial state. used for "logical" initialization code
    return {perMinute: '-', perDay: '-'};
  },
  componentDidMount: function() {
    // fired only once, when the component is added to the DOM
    // used for initialization code that has "side effects" i.e. i/o, jquery plugins, etc
    var socket = io.connect(this.props.url);

petehunt

/** @jsx React.DOM */
var MyRootComponent = React.createClass({
  getInitialState: function() {
    return {perMinute: '-', perDay: '-'};
  },
  componentDidMount: function() {
    var socket = io.connect(this.props.url);
    socket.on('business.clickout', this.setState.bind(this));
  },
  render: function() {