Authored by Peter Rybin , Chrome DevTools team
In this short guide we'll review some new Chrome DevTools features for "function scope" and "internal properties" by exploring some base JavaScript language concepts.
Let's start with closures – one of the most famous things in JS. A closure is a function, that uses variables from outside. See an example:
| # Usage: redis-cli publish message.achannel hello | |
| require 'sinatra' | |
| require 'redis' | |
| conns = Hash.new {|h, k| h[k] = [] } | |
| Thread.abort_on_exception = true | |
| get '/' do |
| Highcharts.Chart.prototype.callbacks.push(function(chart) { | |
| var hasTouch = document.documentElement.ontouchstart !== undefined, | |
| mouseTracker = chart.tracker, | |
| container = chart.container, | |
| mouseMove; | |
| mouseMove = function (e) { | |
| // let the system handle multitouch operations like two finger scroll | |
| // and pinching | |
| if (e && e.touches && e.touches.length > 1) { |
The script below is triggered every day from my Mac. I use Hazel to move the tar.gz to an external hard disk once it's finished. This happens every day without me noticing. You can exclude folders if you want to. You probably want to exclude giant cache folders.
You should have a similar script.
| $module-placeholders-defined: false !default; | |
| @mixin module-placeholders { | |
| @if not $module-placeholders-defined { | |
| $module-placeholders-defined: true; | |
| %module-object { color: red; } | |
| %module-object:hover { color: blue; } | |
| } | |
| } | |
| @include module-placeholders; |
| if environment == :production | |
| on_stylesheet_saved do |file| | |
| # pretty logging output when making a gzipp'ed file | |
| gz_file = Pathname.new("#{file}.gz").relative_path_from(Pathname.new(project_path)) | |
| Compass::Logger.new.record(:create, gz_file) | |
| # This generates a file of the same name but ending in .gz | |
| `gzip -f #{file}` | |
| end | |
| end |
| guard 'rspec', :version => 2 do | |
| watch(%r{^spec/.+_spec\.rb$}) | |
| watch(%r{^lib/(.+)\.rb$}) { |m| "spec/lib/#{m[1]}_spec.rb" } | |
| watch('spec/spec_helper.rb') { "spec" } | |
| # Rails example | |
| watch(%r{^app/(.+)\.rb$}) { |m| "spec/#{m[1]}_spec.rb" } | |
| watch(%r{^app/(.*)(\.erb|\.haml)$}) { |m| "spec/#{m[1]}#{m[2]}_spec.rb" } | |
| watch(%r{^app/controllers/(.+)_(controller)\.rb$}) { |m| ["spec/routing/#{m[1]}_routing_spec.rb", "spec/#{m[2]}s/#{m[1]}_#{m[2]}_spec.rb", "spec/acceptance/#{m[1]}_spec.rb"] } | |
| watch(%r{^spec/support/(.+)\.rb$}) { "spec" } |
| #!/usr/bin/env sh | |
| ## | |
| # This is script with usefull tips taken from: | |
| # https://github.com/mathiasbynens/dotfiles/blob/master/.osx | |
| # | |
| # install it: | |
| # curl -sL https://raw.github.com/gist/2108403/hack.sh | sh | |
| # |
Backstory: I decided to crowdsource static site generator recommendations, so the following are actual real world suggested-to-me results. I then took those and sorted them by language/server and, just for a decent relative metric, their Github Watcher count. If you want a heap of other projects (including other languages like Haskell and Python) Nanoc has the mother of all site generator lists. If you recommend another one, by all means add a comment.
