cd ~/Library/Application\ Support/Sublime\ Text\ 2/Packages
git clone git://github.com/jashkenas/coffee-script-tmbundle CoffeeScript
git clone https://github.com/miksago/jade-tmbundle.git Jade
git clone https://github.com/LearnBoost/stylus.git Stylus
# First install tmux | |
brew install tmux | |
# For mouse support (for switching panes and windows) | |
# Only needed if you are using Terminal.app (iTerm has mouse support) | |
Install http://www.culater.net/software/SIMBL/SIMBL.php | |
Then install https://bitheap.org/mouseterm/ | |
# More on mouse support http://floriancrouzat.net/2010/07/run-tmux-with-mouse-support-in-mac-os-x-terminal-app/ |
// Includes functions for exporting active sheet or all sheets as JSON object (also Python object syntax compatible). | |
// Tweak the makePrettyJSON_ function to customize what kind of JSON to export. | |
var FORMAT_ONELINE = 'One-line'; | |
var FORMAT_MULTILINE = 'Multi-line'; | |
var FORMAT_PRETTY = 'Pretty'; | |
var LANGUAGE_JS = 'JavaScript'; | |
var LANGUAGE_PYTHON = 'Python'; |
A GUI, or rather a CMS interface for DocPad is the big next step. It was also one of the first proof of concepts I used to ensure DocPad would be able to scale into the web development platform of the future.
Back in the first early months of DocPad, I created three plugins:
- Authenticate: To authenticate you against the project's maintainers to ensure that you have read and write access
- REST: Provided authenticated users the ability to update documents via HTTP POST requests using JSON
I want to use YUI inside of a WebWorker thread. Flickr recently wrote a post on this very topic, Web workers and YUI.
But I want to use YUI's CDN, which WebWorkers prevent because it enforces a same-origin policy with importScripts()
# ================================= | |
# DocPad Events | |
# Here we can define handlers for events that DocPad fires | |
# You can find a full listing of events on the DocPad Wiki | |
events: | |
# Server Extend | |
# Used to add our own custom routes to the server before the docpad routes are added | |
serverExtend: (opts) -> |
This article has been given a more permanent home on my blog. Also, since it was first written, the development of the Promises/A+ specification has made the original emphasis on Promises/A seem somewhat outdated.
Promises are a software abstraction that makes working with asynchronous operations much more pleasant. In the most basic definition, your code will move from continuation-passing style:
getTweetsFor("domenic", function (err, results) {
// the rest of your code goes here.
The following will bundle your script assets with browserify each time a generation write completes. The bundled file will be located at my-website/out/scripts.js
if you are using all the default configuration for your paths.
- Install Dependencies
:: 3. Build DocPad Site | |
echo Building the DocPad site | |
pushd %DEPLOYMENT_TARGET% | |
call %DEPLOYMENT_TARGET%\node_modules\.bin\docpad.cmd generate | |
IF !ERRORLEVEL! NEQ 0 goto error |