AaronO

Install cask that extends the brew command :

brew install phinze/cask/brew-cask

Install calibre using cask :

brew cask install calibre

danharper

// this is the background code...

// listen for our browerAction to be clicked
chrome.browserAction.onClicked.addListener(function (tab) {
	// for the current tab, inject the "inject.js" file & execute it
	chrome.tabs.executeScript(tab.ib, {
		file: 'inject.js'
	});
});

dandrews

Accounting
Active Lifestyle
Ad Targeting
Adult
Advanced Materials
Adventure Travel
Advertising
Advertising Exchanges
Advertising Networks
Advertising Platforms

0xjjpa

#Introduction

Developing Chrome Extensions is REALLY fun if you are a Front End engineer. If you, however, struggle with visualizing the architecture of an application, then developing a Chrome Extension is going to bite your butt multiple times due the amount of excessive components the extension works with. Here are some pointers in how to start, what problems I encounter and how to avoid them.

Note: I'm not covering chrome package apps, which although similar, work in a different way. I also won't cover the page options api neither the new brand event pages. What I explain covers most basic chrome applications and should be enough to get you started.

Table of Contents

1. Understand the Chrome Architecture
2. Understand the Tabs-Extension Relationship
3. Picking the right interface for the job

ken47

function perceptron0 = perceptron(numPoints, runs)
  iters = 0;

  for i = 1:runs
    errors = 2;
    points = genPoints(numPoints);
    gWeights = [0 0 0];
    [fWeights,a,b] = genTarget;
    while errors > 0
      errors = 0;

andphe

/usr/bin/plutil -convert xml1 -o - ~/Library/Safari/Bookmarks.plist | grep -E  -o '<string>http[s]{0,1}://.*</string>' | grep -v icloud | sed -E 's/<\/{0,1}string>//g'

cspickert

#!/usr/bin/python

import re, urllib, urllib2

class Spreadsheet(object):
	def __init__(self, key):
		super(Spreadsheet, self).__init__()
		self.key = key

class Client(object):

lancejpollard

What is your folder-structure preference for a large-scale Node.js project?

0: Starting from Rails

This is the reference point. All the other options are based off this.

|-- app
|   |-- controllers
|   |   |-- admin