Description: Setup GitHub Pages "gh-pages" branch and "master" branch as subfolders of a parent project folder ("grandmaster").
Author: Chris Jacob @_chrisjacob
Tutorial (Gist): https://gist.github.com/833223
if (typeof window.localStorage == 'undefined' || typeof window.sessionStorage == 'undefined') (function () { | |
var Storage = function (type) { | |
function createCookie(name, value, days) { | |
var date, expires; | |
if (days) { | |
date = new Date(); | |
date.setTime(date.getTime()+(days*24*60*60*1000)); | |
expires = "; expires="+date.toGMTString(); |
<!DOCTYPE html> | |
<title>Datalist test</title> | |
<meta charset="utf-8"> | |
<form> | |
<label for="source">How did you hear about us?</label> | |
<datalist id="sources"> | |
<select name="source"> | |
<option>please choose...</option> | |
<option value="television">Television</option> | |
<option value="radio">Radio</option> |
Description: Setup GitHub Pages "gh-pages" branch and "master" branch as subfolders of a parent project folder ("grandmaster").
Author: Chris Jacob @_chrisjacob
Tutorial (Gist): https://gist.github.com/833223
Sublime Text 2 ships with a CLI called subl (why not "sublime", go figure). This utility is hidden in the following folder (assuming you installed Sublime in /Applications
like normal folk. If this following line opens Sublime Text for you, then bingo, you're ready.
open /Applications/Sublime\ Text\ 2.app/Contents/SharedSupport/bin/subl
You can find more (official) details about subl here: http://www.sublimetext.com/docs/2/osx_command_line.html
git clone [email protected]:YOUR-USERNAME/YOUR-FORKED-REPO.git
cd into/cloned/fork-repo
git remote add upstream git://github.com/ORIGINAL-DEV-USERNAME/REPO-YOU-FORKED-FROM.git
git fetch upstream
window.matchMedia = window.matchMedia || (function(doc, undefined){ | |
var bool, | |
docElem = doc.documentElement, | |
refNode = docElem.firstElementChild || docElem.firstChild, | |
// fakeBody required for <FF4 when executed in <head> | |
fakeBody = doc.createElement('body'), | |
div = doc.createElement('div'); | |
div.id = 'mq-test-1'; |
<!DOCTYPE html> | |
<html> | |
<head> | |
<meta charset="utf-8"> | |
<title>Single point of breakpoint-definition</title> | |
<style> | |
/* | |
Baseline: | |
*/ |
if (!document.querySelectorAll) { | |
document.querySelectorAll = function(selector) { | |
var doc = document, | |
head = doc.documentElement.firstChild, | |
styleTag = doc.createElement('STYLE'); | |
head.appendChild(styleTag); | |
doc.__qsaels = []; | |
styleTag.styleSheet.cssText = selector + "{x:expression(document.__qsaels.push(this))}"; | |
window.scrollBy(0, 0); |
Last week I attempted to use the CSS sprites feature of Compass for the second or third time. It's been a struggle each time, but the power and potential is there, so I keep coming back. This time was a bit different, though, because I finally decided to stop relying on the docs and dive into the code.
Before I go into the nitty-gritty, let's take a step back and talk about why I
#!/bin/bash | |
## Generate CSS Statistics and determine the health of your css | |
## | |
## Usage | |
## bash /path/to/css-stats-ack.sh | |
## bash /path/to/css-stats-ack.sh > file.txt | |
## | |
## TODO - add support for SCSS | |
## |