Tested in Mac OS X: super == command
Open/Goto
- super+t: go to file
- super+ctrl+p: go to project
- super+r: go to methods
javascript:void(function(){window.location='http://responsinator.com/%3Furl='+encodeURIComponent(window.location.href);})(); |
var getFiletype = function(string){ | |
var lastPeriod = string.lastIndexOf('.') + 1, //char after . | |
length = string.length, | |
diff = length - lastPeriod; | |
if (lastPeriod > 0 && diff <=5) { | |
return string.substring(lastPeriod,length); | |
} | |
}; | |
var filetype = getFiletype(url); |
2012-11-03T12:54:47+00:00 heroku[slugc]: Slug compilation started | |
2012-11-03T12:55:00+00:00 heroku[slugc]: Slug compilation finished | |
^[[1;9C2012-11-03T12:55:51+00:00 heroku[web.1]: Unidling | |
2012-11-03T12:55:51+00:00 heroku[web.1]: State changed from down to starting | |
2012-11-03T12:55:52+00:00 heroku[web.1]: Starting process with command `bundle exec rackup config.ru -p 17663` | |
2012-11-03T12:55:54+00:00 app[web.1]: DEPRECATION WARNING: ActiveSupport::Memoizable is deprecated and will be removed in future releases,simply use Ruby memoization pattern instead. (called from require at /app/config.ru:14) | |
2012-11-03T12:55:54+00:00 app[web.1]: [2012-11-03 12:55:54] INFO WEBrick 1.3.1 | |
2012-11-03T12:55:54+00:00 app[web.1]: [2012-11-03 12:55:54] INFO ruby 1.9.2 (2011-07-09) [x86_64-linux] | |
2012-11-03T12:55:54+00:00 app[web.1]: [2012-11-03 12:55:54] INFO WEBrick::HTTPServer#start: pid=2 port=4000 | |
2012-11-03T12:55:54+00:00 heroku[web.1]: Error R11 (Bad bind) -> Process bound to port 4000, should be 17663 (see environment |
An upgrade failed, now upon trying to reinstall yeoman | |
npm install -g yeoman | |
I get to a point in the installation where it fails on the lookup of the packages. | |
npm ERR! fetch failed http://nodeload.github.com/yeoman/generators/tarball/3d709c61cd | |
npm ERR! fetch failed http://nodeload.github.com/gruntjs/grunt/tarball/0ba6d4b529 | |
npm http 304 https://registry.npmjs.org/rimraf | |
npm http 304 https://registry.npmjs.org/bower | |
npm http 304 https://registry.npmjs.org/mkdirp |
// 01092013 KB | |
var MAGOV = window.MAGOV = window.MAGOV || {}; //namespace custom scripts | |
jQuery(document).ready(function ($) { | |
"use strict"; | |
//fitVids plugin for YT, iframe embeds | |
$(".container").fitVids(); |
[core] | |
editor = subl | |
autocrlf = input | |
safecrlf = true | |
[color] | |
diff = auto | |
status = auto | |
branch = auto |
A curated list by Eric Elliott and friends. Suggest links in the comments below.
This is a very exclusive collection of only must-have JavaScript links. I'm only listing my favorite links. Nothing else makes the cut. Feel free to suggest links if you think they're good enough to make this list. The really curious should feel free to browse the comments to find other links. I can't guarantee the quality of links in the comments.
Some of these links are affiliate links, meaning that if you make a purchase, I might earn a little money. This has absolutely no bearing on whether or not links make the list. None, whatsoever. However, it does allow me more resources to fight poverty with code. Every little bit counts.
This example shows how it is possible to use a D3 sunburst visualization (partition layout) with data that describes sequences of events.
A good use case is to summarize navigation paths through a web site, as in the sample synthetic data file (visit_sequences.csv). The visualization makes it easy to understand visits that start directly on a product page (e.g. after landing there from a search engine), compared to visits where users arrive on the site's home page and navigate from there. Where a funnel lets you understand a single pre-selected path, this allows you to see all possible paths.
Features: