starstuck

#!/usr/bin/env python
# -*- coding: utf8 -*-
#
# Read humidity and temperature from DHT11 sensor connected to RaspberryPi.
#
# DHT11 protocol depends on exact timing. Sometimes linux kernel may evict your
# process, or GC can cause program to miss some of a bits from transmission. In
# that case following application will raise an error and you can try to run it
# again
#

starstuck

#!/usr/bin/env bash
#
# Following script will work with tags preficed with svn, having mapping like:
#     tags = project/tags/*:refs/remotes/svn/tags/*
# If you use differnet paths mapping, you may need to adjust it a bit.
#

git for-each-ref --shell --format='parent=%(parent) refname=%(refname)' refs/remotes/svn/tags/ | \
while read entry
do

starstuck

/**
 * Web application debug proxy server.
 * 
 * It is suited for hosting uncompressed sources of front-end assets and proxy dynamic
 * requests to servers preparing data. I find similar setup also useful for investigating
 * issues on production servers by going through the proxy, which use local unminified
 * JS and CSS on top of production html pages.
 *
 * To run following example you will need to have http-proxy, express and send packages installed.
 *

starstuck

/**
 * To run it you will need to install
 *
 *     $ npm install http-proxy
 */

var http        = require('http'),
    httpProxy   = require('http-proxy'),
    port        = 3001,
    proxiedHost = 'localhost',

starstuck

/**
 * Mouse wheel polyfill inspired by cross-browser example on mdn wiki. 
 *
 * It supports relatively modern browsers, which already support addEventListener and Array forEach methods.
 * Effectively it is targeting webkit based browsers. I didn't have opportunity to test it on old Firefox.
 * Method addEventListener is supported in IE9, which already supports wheel event. I guess one could combine
 * it with polyfill for addEventListener to have support in IE 6-8. In that case one would have to also wrap
 * all addEventListener methods provided by the polyfill (last block below).
 *
 * @see https://developer.mozilla.org/en-US/docs/Web/Reference/Events/wheel?redirectlocale=en-US&redirectslug=DOM%2FMozilla_event_reference%2Fwheel#Listening_to_this_event_across_browser

starstuck

starstuck

;; Define various js test/linting compilation errrors matchers. You can say, 
;; which you want to consider on matching output from compilation, by
;; customizing compilation-error-regexp-alist variable.
;;  
;;   (setq compilation-error-regexp-alist (list 'jstestdriver 'jslint-file 'jslint-line))
;;
;; If you are using desktop.el, you may want to keep compilation customizations
;; in your project deskto file
;;
;;   (add-to-list 'desktop-globals-to-save 'compilation-search-path)

starstuck

#!/usr/bin/env node

var server = require('./test-server'),
    child_process = require('child_process'),

	port = server.port;

console.log('');
console.log('------------------------------------------------------------------------');
console.log('Running jasmine tests in phantomjs');

starstuck

#!/usr/bin/env node

var exec = require('child_process').exec,
    mkdirp = require('mkdirp'),
	projectPath = __dirname + '/../..',
	targetPath = __dirname + '/../../target/assets';

// Task execution helpers
// ----------------------

starstuck

#!/usr/bin/env sh

SYMBOL="[a-zA-Z_][a-zA-Z0-9_]*"
CAP_SYMBOL="[A-Z][a-zA-Z0-9_]*"
GLOB_SYMBOL="${CAP_SYMBOL}\(\.${SYMBOL}\)*"

if [ -z "$1" ]; then
    echo "You need to provide at list one path where to search for js files" 1>&2
    exit 1
fi