Potherca

/*global QUnit, window, document*/
(function (QUnit, window, document) {
    'use strict';

    QUnit.testSkip = function (p_sTestName) {
        QUnit.test(p_sTestName + ' (SKIPPED)', 0, function () {
            var li = document.getElementById(QUnit.config.current.id);
            QUnit.done(function () {
                li.style.background = '#FFFF99';
            });

Potherca

# Add this config
$ heroku config:add LD_LIBRARY_PATH=/app/php/ext:/app/apache/lib

# Login to Heroku CLI
$ heroku run bash

# The second argument here is the path to your script
~ $ ~/php/bin/php -f ~/www/index.php

Potherca

/**
 * Footer for Potherca
 */
@import url(http://fonts.googleapis.com/css?family=Droid+Sans|Droid+Sans+Mono);

.created-by{
	background-color:rgb(255,255,255);
	border-radius:0.35em;
	color:inherit;
	font-family:'Droid Sans', Arial, sans-serif;

Potherca

/**
 * Gravatar as fullscreen background image
 *
 * http://dabblet.com/gist/dab7cdd9f9fcfd093199/1c0636877b6081af33f698740a720e9d25ece924
 */

body {
    position: absolute;
    top: 0; bottom: 0; left: 0; right: 0;
    height: 100%;

Potherca

Badges for Project Stages

Introduction

As any active software developer, I tend to have a lot of projects laying about. With the advent of Github all of these projects now live in the public eye.

For me, as the author, it isn't dificult to keep track of which project is in which state of production. For the casual visitor of my project pages this is a different matter.

To help passers-by to identify how solid a certain project is at-a-glance, I felt it would be prudent to offer them a "Badge". Some uniform way of knowing what to expect of the code in the repository without even having to look at it.

Potherca

Keybase proof

I hereby claim:

• I am potherca on github.
• I am potherca (https://keybase.io/potherca) on keybase.
• I have a public key whose fingerprint is C878 1AE1 5AE4 527F 85CA D253 74A7 6635 76B3 B461

To claim this, I am signing this object:

Potherca

Introduction

In the documentation for [ASCIIToSVG][1], in regards to formatting (shape, color, style, etc.) it's [author][2] wrote:

If you have thoughts on how to do this for lines, please do let me know.

Well... I may have a suggestion.

Format for boxes

Potherca

/**
 * Test for rebeccapurple support
 */

@import url(http://fonts.googleapis.com/css?family=Satisfy);

body {
	background: rebeccapurple;
	min-height: 100%;
}

Potherca

Although I would like to use ARC, I really dislike that it uses SimplTest.
Using http://docs.moodle.org/dev/SimpleTest_conversion as a starting point a migration to PhpUnit seems rather trivial...

Potherca

On the subject of omitting units (%, px, em, etc.) after zeros or not, I am a proponent of omitting the unit.

For me this is a case of

• Brevity
• Clarity
• Error-proneness
• Readability
• Validity