Steffen Bruchmann sbruchmann

Description

This simple script will take a picture of a whiteboard and use parts of the ImageMagick library with sane defaults to clean it up tremendously.

The script is here:

#!/bin/bash
convert "$1" -morphology Convolve DoG:15,100,0 -negate -normalize -blur 0x1 -channel RBG -level 60%,91%,0.1 "$2"

Results

Deploy a subdirectory in your NodeJS Git project to GitHub pages.

Make sure node build outputs some static files to _built.
npm run deploy.

This eventually became this blog post and this module

I wanted to figure out the fastest way to load non-critical CSS so that the impact on initial page drawing is minimal.

TL;DR: Here's the solution I ended up with: https://github.com/filamentgroup/loadCSS/

For async JavaScript file requests, we have the async attribute to make this easy, but CSS file requests have no similar standard mechanism (at least, none that will still apply the CSS after loading - here are some async CSS loading conditions that do apply when CSS is inapplicable to media: https://gist.github.com/igrigorik/2935269#file-notes-md ).

Seems there are a couple ways to load and apply a CSS file in a non-blocking manner:

The final result: require() any module on npm in your browser console with browserify

This article is written to explain how the above gif works in the chrome (and other) browser consoles. A quick disclaimer: this whole thing is a huge hack, it shouldn't be used for anything seriously, and there are probably much better ways of accomplishing the same.

Update: There are much better ways of accomplishing the same, and the script has been updated to use a much simpler method pulling directly from browserify-cdn. See this thread for details: mathisonian/requirify#5

inspiration

Styling native elements

Native HTML controls are a challenge to style. You can style any element in the web platform that uses Shadow DOM with a pseudo element ::pseudo-element or the /deep/ path selector.

video::webkit-media-controls-timeline {
  background-color: lime;
}

video /deep/ input[type=range] {

In all the discussions about ES6 one thing is bugging me. I'm picking one random comment here from this io.js issue but it's something that comes up over and over again:

There's sentiment from one group that Node should have full support for Promises. While at the same time another group wants generator syntax support (e.g. var f = yield fs.stat(...)).

People keep putting generators, callbacks, co, thunks, control flow libraries, and promises into one bucket. If you read that list and you think "well, they are all kind of doing the same thing", then this is to you.

	if (downloadRatio < 1.0) {
	self.debug.log("Download ratio is poor.");
	if (current > 0) {
	self.debug.log("We are not at the lowest bitrate, so switch down.");
	self.manifestExt.getRepresentationFor(current - 1, data).then(
	function (representation1) {
	self.manifestExt.getBandwidth(representation1).then(
	function (oneDownBandwidth) {
	self.manifestExt.getRepresentationFor(current, data).then(
	function (representation2) {

	var Promise = require('bluebird');

	var promiseWhile = function(condition, action) {
	var resolver = Promise.defer();

	var loop = function() {
	if (!condition()) return resolver.resolve();
	return Promise.cast(action())
	.then(loop)
	.catch(resolver.reject);

	.container {
	height: 500px;
	border: 2px solid grey;
	position:relative;
	}

	.split {
	display: flex;
	height: 100%;
	border: 1px solid black;

	#!/bin/sh

	# Check to see if we are on master branch. Stop accidental commits
	if [ $(git symbolic-ref HEAD 2>/dev/null) == "refs/heads/master" ]
	then
	echo "Cannot commit to master branch"
	exit 1
	fi
	exit 0