Create droplet of your liking (ubuntu 12.10 x32)
ssh to root in terminal with your server ip
ssh [email protected]
Add ssh fingerprint and enter password provided in email
module.exports = function(grunt) { | |
// Project configuration. | |
grunt.initConfig({ | |
compass: { | |
dist: { | |
options: { | |
sassDir: 'sass', | |
cssDir: 'css', | |
environment: 'production' | |
} |
Create droplet of your liking (ubuntu 12.10 x32)
ssh to root in terminal with your server ip
ssh [email protected]
Add ssh fingerprint and enter password provided in email
// Start `node d3-server.js` | |
// Then visit http://localhost:1337/ | |
// | |
var d3 = require('d3'), | |
http = require('http') | |
http.createServer(function (req, res) { | |
// Chrome automatically sends a requests for favicons | |
// Looks like https://code.google.com/p/chromium/issues/detail?id=39402 isn't | |
// fixed or this is a regression. |
import processing.serial.*; | |
int SIDE_LENGTH = 1000; | |
int ANGLE_BOUNDS = 80; | |
int ANGLE_STEP = 2; | |
int HISTORY_SIZE = 10; | |
int POINTS_HISTORY_SIZE = 500; | |
int MAX_DISTANCE = 100; | |
int angle; |
There are a bunch of reasons why this is convoluted, mostly in building the URL to make the request:
info_format
parameter in the request. We don't know a priori which will be supported by a WMS that we might make a request to. See Geoserver's docs for what formats are available from Geoserver. That won't be the same from WMS to WMS, however.package org.kt3k.bankaccount; | |
public class BankAccount { | |
private String id; | |
private Integer balance; | |
public BankAccount(String id, Integer balance) { | |
this.id = id; | |
this.balance = balance; |
describe('e2e: main', function() { | |
var ptor; | |
beforeEach(function() { | |
browser.get('/'); | |
ptor = protractor.getInstance(); | |
}); | |
it('should load the home page', function() { |
/*! | |
* gulp | |
* $ npm install gulp-ruby-sass gulp-autoprefixer gulp-cssnano gulp-jshint gulp-concat gulp-uglify gulp-imagemin gulp-notify gulp-rename gulp-livereload gulp-cache del --save-dev | |
*/ | |
// Load plugins | |
var gulp = require('gulp'), | |
sass = require('gulp-ruby-sass'), | |
autoprefixer = require('gulp-autoprefixer'), | |
cssnano = require('gulp-cssnano'), |
This post also appears on lisper.in.
Reader macros are perhaps not as famous as ordinary macros. While macros are a great way to create your own DSL, reader macros provide even greater flexibility by allowing you to create entirely new syntax on top of Lisp.
Paul Graham explains them very well in [On Lisp][] (Chapter 17, Read-Macros):
The three big moments in a Lisp expression's life are read-time, compile-time, and runtime. Functions are in control at runtime. Macros give us a chance to perform transformations on programs at compile-time. ...read-macros... do their work at read-time.
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.