ingoradatz

L.Control.Button = L.Control.extend({
  options: {
    position: 'bottomleft'
  },
  initialize: function (options) {
    this._button = {};
    this.setButton(options);
  },

ingoradatz

jQuery.fn.brightness = function() {
  var bg_color, rgba, y;
  bg_color = this.css('background-color');
  if ((bg_color != null) && bg_color.length) {
    rgba = bg_color.match(/^rgb(?:a)?\(([0-9]{1,3}),\s([0-9]{1,3}),\s([0-9]{1,3})(?:,\s)?([0-9]{1,3})?\)$/);
    if (rgba != null) {
      if (rgba[4] === '0') {
        if (this.parent().length) return this.parent().brightness();
      } else {
        y = 2.99 * rgba[1] + 5.87 * rgba[2] + 1.14 * rgba[3];

ingoradatz

// data comes from here http://stat-computing.org/dataexpo/2009/the-data.html
// download 1994.csv.bz2 and unpack by running: cat 1994.csv.bz2 | bzip2 -d > 1994.csv
// 1994.csv should be ~5.2 million lines and 500MB
// importing all rows into leveldb took ~50 seconds on my machine

// there are two main techniques at work here:
// 1: never create JS objects, leave the data as binary the entire time (binary-split does this)
// 2: group lines into 16 MB batches, to take advantage of leveldbs batch API (byte-stream does this)

var level = require('level')

ingoradatz

_

ingoradatz

How to set up stress-free SSL on an OS X development machine

One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.

Most workflows make the following compromises:

• Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.

• Use production SSL certificates locally. This is annoying

ingoradatz

(function(){


    var currentETag;

    onLoad(function pageLoaded() {
        console.log('starting live reload');
        if (window.EventSource) return eventsource();
        else setInterval(polling, 1500);
    });

ingoradatz

1) have the couchdb source available, geocouch needs some headerfiles

2) get and unpack the appropriate branch of geocouch suited for your couchdb version -
   I have 1.3.0 so I got
   
   https://github.com/couchbase/geocouch/tree/couchdb1.3.x

3) set environment:

   export COUCH_SRC=/WHEREVER/apache-couchdb-1.3.0/src/couchdb/

ingoradatz

#!/usr/bin/perl
use 5.008;
use strict;
use Memoize;

sub usage { die "usage: git-large-blob <size[b|k|m]> [<git-log arguments ...>]\n" }

@ARGV or usage();
my ( $max_size, $unit ) = ( shift =~ /^(\d+)([bkm]?)\z/ ) ? ( $1, $2 ) : usage();

ingoradatz

// Short module explanation             // Something to gather my thoughts
//                                      // I think this looks cool.
                                        //
module.exports = the_exported_function  // Modules are a function. Always.
                                        //
module.exports.extra = extra            // Additional API entry points if
module.exports.other = other            // desired.
                                        //
var util = require('util')              // Other packages from npm or core
var assert = require('assert')          // No comma-first due to lots of

ingoradatz

var mapLink = "http://maps.google.com/maps?z=12&t=m&q=loc:" + lat + "+" + lon
if ($.os.ios && navigator.userAgent.match(/iPhone OS 6_/)) mapLink = "Maps://?q=" + lat + "," + lon
if ($.os.android) mapLink = "geo:" + lat + "," + lon + "?z=12&q=" + lat + "," + lon


// assumes you have zepto and zepto.detect loaded
// also you should use target=_blank on your <a> tags