Kun Liang ahliang85

## debounce_1.js
function debounce(fn, delay) {
  var timer = null;
  return function () {
    var context = this, args = arguments;
    clearTimeout(timer);
    timer = setTimeout(function () {
      fn.apply(context, args);
    }, delay);
  };
}

## once.js
// http://davidwalsh.name/javascript-once

function once(fn, context) {
	var result;

	return function() {
		if(fn) {
			result = fn.apply(context || this, arguments);
			fn = null;
		}

## XMLHttpRequest.html
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="X-UA-Compatible" content="IE=Edge, chrome=1"/>
<script>
"use strict";
function submitForm(oFormElement)
{
  var xhr = new XMLHttpRequest();
  xhr.onload = function(){ alert (xhr.responseText); }

## imageOptim.command
# imageoptim --image-alpha --jpeg-mini --quit --directory ~/Sites/MyProject

# shorthand format:
# imageoptim -a -j -q -d ~/Sites/MyProject

## modify-dom.txt
Background page is kind of like you own mini server - it is a completely isolated page that has nothing to do with pages a user visits. It is used for controlling the rest of extension components as it is always running in background.

Content scripts are pieces of javascript code that are getting injected into actual pages a user visits and can access and modify parent page's DOM.

So to get your extension working you need to remove

<script src="jquery.min.js"></script>
<script src="content.js"></script>
from background page, and inject jquery as a content script either through manifest:

## move-to-gif.command
ffmpeg -i in.mov -s 600x400 -pix_fmt rgb24 -r 10 -f gif - | gifsicle --optimize=3 --delay=3 > out.gif

## rAF-2.js
// shim layer with setTimeout fallback
window.requestAnimFrame = (function(){
  return  window.requestAnimationFrame       ||
          window.webkitRequestAnimationFrame ||
          window.mozRequestAnimationFrame    ||
          function( callback ){
            window.setTimeout(callback, 1000 / 60);
          };
})();
	function debounce(fn, delay) {
	var timer = null;
	return function () {
	var context = this, args = arguments;
	clearTimeout(timer);
	timer = setTimeout(function () {
	fn.apply(context, args);
	}, delay);
	};
	}
	// http://davidwalsh.name/javascript-once

	function once(fn, context) {
	var result;

	return function() {
	if(fn) {
	result = fn.apply(context \|\| this, arguments);
	fn = null;
	}
	<!DOCTYPE html>
	<html>
	<head>
	<meta http-equiv="X-UA-Compatible" content="IE=Edge, chrome=1"/>
	<script>
	"use strict";
	function submitForm(oFormElement)
	{
	var xhr = new XMLHttpRequest();
	xhr.onload = function(){ alert (xhr.responseText); }
	# imageoptim --image-alpha --jpeg-mini --quit --directory ~/Sites/MyProject

	# shorthand format:
	# imageoptim -a -j -q -d ~/Sites/MyProject
	Background page is kind of like you own mini server - it is a completely isolated page that has nothing to do with pages a user visits. It is used for controlling the rest of extension components as it is always running in background.

	Content scripts are pieces of javascript code that are getting injected into actual pages a user visits and can access and modify parent page's DOM.

	So to get your extension working you need to remove

	<script src="jquery.min.js"></script>
	<script src="content.js"></script>
	from background page, and inject jquery as a content script either through manifest:
	// shim layer with setTimeout fallback
	window.requestAnimFrame = (function(){
	return window.requestAnimationFrame \|\|
	window.webkitRequestAnimationFrame \|\|
	window.mozRequestAnimationFrame \|\|
	function( callback ){
	window.setTimeout(callback, 1000 / 60);
	};
	})();