handlebars 0.0.2 → 0.2.0

data/.gitignore

@@ -1,4 +1,4 @@
 pkg/*
 *.gem
 .bundle
-session.vim
+Gemfile.lock

data/.gitmodules

@@ -0,0 +1,3 @@
+[submodule "vendor/handlebars"]
+	path = vendor/handlebars
+	url = https://github.com/wycats/handlebars.js.git

data/.rspec

@@ -0,0 +1 @@
+--colour

data/Gemfile

@@ -1,4 +1,4 @@
-source :gemcutter
+source "http://rubygems.org"
 
 # Specify your gem's dependencies in handlebars.gemspec
 gemspec

data/README.mdown

@@ -0,0 +1,44 @@
+
+## Handlebars.rb
+
+This uses [therubyracer][1] to bind to the _actual_ JavaScript implementation of
+[Handlebars.js][2] so that you can use it from ruby.
+
+## Usage
+
+Simple stuff
+
+    require 'handlebars'
+    template = Handlebars.compile("{{say}}{{what}}")
+    template.call(:say => "Hey", :what => "Yuh!") #=> "Hey Yuh!"
+
+With functions as properties
+
+    template.call(:say => "Hey", :what => lambda {|this| ("yo" * 2) + "!"}) #=> "Hey yoyo!"
+
+Register block helpers:
+
+    Handlebars.register_helper(:twice) do |block|
+      "#{block.call}#{block.call}"
+    end
+    template = Handlebars.compile({{#twice}}Hurray!{{/twice}})
+    template.call #=> Hurray!Hurray!
+
+## Hack
+
+    git clone git@github.com:cowboyd/handlebars.rb.git #git it
+    cd handlebars.rb #go to it
+    git submodule update --init #pull down handlebars.js
+    rspec spec/ #test it
+
+
+## Rubygems
+
+  Handlebars is available via the [hbs][3] gem on rubygems.org. There is also a
+  [handlebars][4] gem, which is a pure-ruby implementation that appears to no longer be maintained.
+
+[1]: http://github.com/cowboyd/therubyracer "The Ruby Racer"
+[2]: http://github.com/wycats/handlebars.js "Handlebars JavaScript templating library"
+[3]: http://rubygems.org/gems/hbs "handelbars gem in JavaScript"
+[4]: http://rubygems.org/gems/handlebars "pure ruby handlebars gem"
+

data/Rakefile

@@ -1,2 +1,5 @@
 require 'bundler'
 Bundler::GemHelper.install_tasks
+
+require 'rspec/core/rake_task'
+RSpec::Core::RakeTask.new(:spec)

data/handlebars.gemspec

@@ -1,23 +1,29 @@
 # -*- encoding: utf-8 -*-
-require File.expand_path("../lib/handlebars/version", __FILE__)
+$:.push File.expand_path("../lib", __FILE__)
+require "handlebars/version"
 
 Gem::Specification.new do |s|
   s.name        = "handlebars"
   s.version     = Handlebars::VERSION
   s.platform    = Gem::Platform::RUBY
-  s.authors     = ['Martin Schuerrer']
-  s.email       = ['martin@schuerrer.org']
-  s.homepage    = "http://github.com/MSch/handlebars-ruby"
-  s.summary     = "handlebars.js port to ruby"
-  s.description = "A straight port of handlebars.js to ruby. Currently unfinished, if you've got a complete version let me know so I'll release the name to you"
+  s.authors     = ["Charles Lowell"]
+  s.email       = ["cowboyd@thefrontside.net"]
+  s.homepage    = "http://github.com/cowboyd/handlebars.rb"
+  s.summary     = %q{Ruby bindings for the handlebars.js templating library}
+  s.description = %q{Uses the actual JavaScript implementation of Handlebars, but supports using Ruby objects as template contexts and Ruby procs as view functions and named helpers}
 
-  s.required_rubygems_version = ">= 1.3.6"
-  s.rubyforge_project         = "handlebars"
+  s.rubyforge_project = "handlebars"
 
-  s.add_development_dependency "bundler", ">= 1.0.0"
-  s.add_development_dependency "rspec", "~> 2.0.0"
+  s.files         = `git ls-files`.split("\n")
+  s.test_files    = `git ls-files -- {test,spec,features}/*`.split("\n")
+  s.executables   = `git ls-files -- bin/*`.split("\n").map{ |f| File.basename(f) }
+  s.require_paths = ["lib"]
+  Dir.chdir("vendor/handlebars") do
+    s.files += `git ls-files`.split("\n").map {|f| "vendor/handlebars/#{f}"}
+    s.files += ['vendor/handlebars/lib/handlebars/compiler/parser.js']
+  end
 
-  s.files        = `git ls-files`.split("\n")
-  s.executables  = `git ls-files`.split("\n").map{|f| f =~ /^bin\/(.*)/ ? $1 : nil}.compact
-  s.require_path = 'lib'
+  s.add_dependency "therubyracer", "~> 0.10.0beta1"
+  s.add_dependency "commonjs", "~> 0.2.3"
+  s.add_development_dependency "rspec", "~> 2.0"
 end

data/lib/handlebars.rb

@@ -1,5 +1,6 @@
-require 'handlebars/generator'
-require 'handlebars/parser'
 
-class Handlebars
+require 'handlebars/loader'
+
+module Handlebars
+    autoload :Context,  'handlebars/context'
 end

data/lib/handlebars/context.rb

@@ -0,0 +1,37 @@
+require 'commonjs'
+
+module Handlebars
+  class Context
+    def initialize
+      @js = CommonJS::Environment.new V8::Context.new, :path => [
+        File.expand_path('../../../vendor/bootstrap', __FILE__),
+        File.expand_path('../../../vendor/handlebars/lib', __FILE__)
+      ]
+      
+      # This is a slightly modified version of handlebars.js found in the main
+      # distribution. The Ruby commonjs environment does not support full directory
+      # requires, so we expand them by hand. Eventually this may be fixed upstream
+      # but right now I'm not sure if this is a node-specific extension.
+
+      @js.require('handlebars/base')
+      @js.require('handlebars/utils')
+      for compiler_module in %w(ast base compiler index parser printer visitor)
+        @js.require("handlebars/compiler/#{compiler_module}")
+      end
+      @js.require('handlebars/runtime')
+    end
+    
+    def compile(*args)
+      handlebars.compile(*args)
+    end
+
+    def register_helper(name, &fn)
+      handlebars.registerHelper(name, fn)
+    end
+
+    def handlebars
+      @js.require('handlebars/base')
+    end
+
+  end
+end

data/lib/handlebars/version.rb

@@ -1,3 +1,3 @@
 module Handlebars
-  VERSION = "0.0.2"
+  VERSION = "0.2.0"
 end

data/spec/handlebars_spec.rb

@@ -0,0 +1,40 @@
+
+require 'handlebars'
+describe(Handlebars::Context) do
+
+  describe "a simple template" do
+    let(:t) {subject.compile("Hello {{name}}")}
+    it "allows simple subsitution" do
+      t.call(:name => 'World').should eql "Hello World"
+    end
+
+    it "allows Ruby blocks as a property" do
+      t.call(:name => lambda {|context| ;"Mate"}).should eql "Hello Mate"
+    end
+
+    it "can use any Ruby object as a context" do
+      t.call(mock(:Object, :name => "Flipper")).should eql "Hello Flipper"
+    end
+  end
+
+  describe "registering Helpers" do
+    before do
+      subject.register_helper('alsowith') do |this, context, block|
+        block.call(context)
+      end
+      subject.register_helper(:twice) do |this, block|
+        "#{block.call}#{block.call}"
+      end
+    end
+
+    it "correctly passes context and implementation" do
+      t = subject.compile("it's so {{#alsowith weather}}*{{summary}}*{{/alsowith}}!")
+      t.call(:weather => {:summary => "sunny"}).should eql "it's so *sunny*!"
+    end
+
+    it "doesn't nee a context or arguments to the call" do
+      t = subject.compile("{{#twice}}Hurray!{{/twice}}")
+      t.call.should eql "Hurray!Hurray!"
+    end
+  end
+end

data/spike.rb

@@ -0,0 +1,17 @@
+require 'handlebars'
+
+Handlebars.register_helper "table" do |block|
+ "<table>#{block.call}</table>"
+end
+
+Handlebars.register_helper "row" do |block|
+  "<tr class='awesome-row'>#{block.call}</tr>"
+end
+
+t = Handlebars.compile <<-HBS
+{{#table width}}
+  {{#row}}<td>Hi</td>{{/row}}
+{{/table}}
+HBS
+
+puts t.call

data/vendor/handlebars/.gitignore

@@ -0,0 +1,6 @@
+dist
+vendor
+.rvmrc
+.DS_Store
+lib/handlebars/compiler/parser.js
+node_modules

data/vendor/handlebars/.jshintrc

@@ -0,0 +1,50 @@
+{
+    "predef": [
+        "console",
+        "Ember",
+        "DS",
+        "Handlebars",
+        "Metamorph",
+        "ember_assert",
+        "ember_warn",
+        "ember_deprecate",
+        "ember_deprecateFunc",
+        "require",
+        "equal",
+        "test",
+        "testBoth",
+        "raises",
+        "deepEqual",
+        "start",
+        "stop",
+        "ok",
+        "strictEqual",
+        "module"
+    ],
+
+    "node" : true,
+    "es5" : true,
+    "browser" : true,
+
+    "boss" : true,
+    "curly": false,
+    "debug": false,
+    "devel": false,
+    "eqeqeq": true,
+    "evil": true,
+    "forin": false,
+    "immed": false,
+    "laxbreak": false,
+    "newcap": true,
+    "noarg": true,
+    "noempty": false,
+    "nonew": false,
+    "nomen": false,
+    "onevar": false,
+    "plusplus": false,
+    "regexp": false,
+    "undef": true,
+    "sub": true,
+    "strict": false,
+    "white": false
+}

data/vendor/handlebars/.npmignore

@@ -0,0 +1,11 @@
+.DS_Store
+.gitignore
+.rvmrc
+Gemfile
+Gemfile.lock
+Rakefile
+bench/*
+dist/*
+spec/*
+src/*
+vendor/*

data/vendor/handlebars/Gemfile

@@ -0,0 +1,5 @@
+source "http://rubygems.org"
+
+gem "rake"
+gem "therubyracer", ">= 0.9.8"
+gem "rspec"

data/vendor/handlebars/LICENSE

@@ -0,0 +1,20 @@
+Copyright (C) 2011 by Yehuda Katz
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.
+

data/vendor/handlebars/README.markdown

@@ -0,0 +1,315 @@
+[![Build Status](https://secure.travis-ci.org/wycats/handlebars.js.png)](http://travis-ci.org/wycats/handlebars.js)
+
+Handlebars.js
+=============
+
+Handlebars.js is an extension to the [Mustache templating language](http://mustache.github.com/) created by Chris Wanstrath. Handlebars.js and Mustache are both logicless templating languages that keep the view and the code separated like we all know they should be.
+
+Checkout the official Handlebars docs site at [http://www.handlebarsjs.com](http://www.handlebarsjs.com).
+
+
+Installing
+----------
+Installing Handlebars is easy. Simply [download the package from GitHub](https://github.com/wycats/handlebars.js/archives/master) and add it to your web pages (you should usually use the most recent version).
+
+Usage
+-----
+In general, the syntax of Handlebars.js templates is a superset of Mustache templates. For basic syntax, check out the [Mustache manpage](http://mustache.github.com/mustache.5.html).
+
+Once you have a template, use the Handlebars.compile method to compile the template into a function. The generated function takes a context argument, which will be used to render the template.
+
+```js
+var source = "<p>Hello, my name is {{name}}. I am from {{hometown}}. I have " + 
+             "{{kids.length}} kids:</p>" +
+             "<ul>{{#kids}}<li>{{name}} is {{age}}</li>{{/kids}}</ul>";
+var template = Handlebars.compile(source);
+
+var data = { "name": "Alan", "hometown": "Somewhere, TX",
+             "kids": [{"name": "Jimmy", "age": "12"}, {"name": "Sally", "age": "4"}]};
+var result = template(data);
+
+// Would render:
+// <p>Hello, my name is Alan. I am from Somewhere, TX. I have 2 kids:</p>
+// <ul>
+//   <li>Jimmy is 12</li>
+//   <li>Sally is 4</li>
+// </ul>
+```
+
+
+Registering Helpers
+-------------------
+
+You can register helpers that Handlebars will use when evaluating your
+template. Here's an example, which assumes that your objects have a URL
+embedded in them, as well as the text for a link:
+
+```js
+Handlebars.registerHelper('link_to', function(context) {
+  return "<a href='" + context.url + "'>" + context.body + "</a>";
+});
+
+var context = { posts: [{url: "/hello-world", body: "Hello World!"}] };
+var source = "<ul>{{#posts}}<li>{{{link_to this}}}</li>{{/posts}}</ul>"
+
+var template = Handlebars.compile(source);
+template(context);
+
+// Would render:
+//
+// <ul>
+//   <li><a href='/hello-world'>Hello World!</a></li>
+// </ul>
+```
+
+Escaping
+--------
+
+By default, the `{{expression}}` syntax will escape its contents. This
+helps to protect you against accidental XSS problems caused by malicious
+data passed from the server as JSON.
+
+To explicitly *not* escape the contents, use the triple-mustache
+(`{{{}}}`). You have seen this used in the above example.
+
+
+Differences Between Handlebars.js and Mustache
+----------------------------------------------
+Handlebars.js adds a couple of additional features to make writing templates easier and also changes a tiny detail of how partials work.
+
+### Paths
+
+Handlebars.js supports an extended expression syntax that we call paths. Paths are made up of typical expressions and . characters. Expressions allow you to not only display data from the current context, but to display data from contexts that are descendents and ancestors of the current context.
+
+To display data from descendent contexts, use the `.` character. So, for example, if your data were structured like:
+
+```js
+var data = {"person": { "name": "Alan" }, company: {"name": "Rad, Inc." } };
+```
+
+you could display the person's name from the top-level context with the following expression:
+
+```
+{{person.name}}
+```
+
+You can backtrack using `../`. For example, if you've already traversed into the person object you could still display the company's name with an expression like `{{../company.name}}`, so:
+
+```
+{{#person}}{{name}} - {{../company.name}}{{/person}}
+```
+
+would render:
+
+```
+Alan - Rad, Inc.
+```
+
+### Strings
+
+When calling a helper, you can pass paths or Strings as parameters. For
+instance:
+
+```js
+Handlebars.registerHelper('link_to', function(title, context) {
+  return "<a href='/posts" + context.id + "'>" + title + "</a>"
+});
+
+var context = { posts: [{url: "/hello-world", body: "Hello World!"}] };
+var source = '<ul>{{#posts}}<li>{{{link_to "Post" this}}}</li>{{/posts}}</ul>'
+
+var template = Handlebars.compile(source);
+template(context);
+
+// Would render:
+//
+// <ul>
+//   <li><a href='/hello-world'>Post!</a></li>
+// </ul>
+```
+
+When you pass a String as a parameter to a helper, the literal String
+gets passed to the helper function.
+
+
+### Block Helpers
+
+Handlebars.js also adds the ability to define block helpers. Block helpers are functions that can be called from anywhere in the template. Here's an example:
+
+```js
+var source = "<ul>{{#people}}<li>{{{#link}}}{{name}}{{/link}}</li>{{/people}}</ul>";
+Handlebars.registerHelper('link', function(context, fn) {
+  return '<a href="/people/' + this.__get__("id") + '">' + fn(this) + '</a>';
+});
+var template = Handlebars.compile(source);
+
+var data = { "people": [
+    { "name": "Alan", "id": 1 },
+    { "name": "Yehuda", "id": 2 }
+  ]};
+template(data);
+
+// Should render:
+// <ul>
+//   <li><a href="/people/1">Alan</a></li>
+//   <li><a href="/people/2">Yehuda</a></li>
+// </ul>
+```
+
+Whenever the block helper is called it is given two parameters, the argument that is passed to the helper, or the current context if no argument is passed and the compiled contents of the block. Inside of the block helper the value of `this` is the current context, wrapped to include a method named `__get__` that helps translate paths into values within the helpers.
+
+### Partials
+
+You can register additional templates as partials, which will be used by
+Handlebars when it encounters a partial (`{{> partialName}}`). Partials
+can either be String templates or compiled template functions. Here's an
+example:
+
+```js
+var source = "<ul>{{#people}}<li>{{> link}}</li>{{/people}}</ul>";
+
+Handlebars.registerPartial('link', '<a href="/people/{{id}}">{{name}}</a>')
+var template = Handlebars.compile(source);
+
+var data = { "people": [
+    { "name": "Alan", "id": 1 },
+    { "name": "Yehuda", "id": 2 }
+  ]};
+
+template(data);
+
+// Should render:
+// <ul>
+//   <li><a href="/people/1">Alan</a></li>
+//   <li><a href="/people/2">Yehuda</a></li>
+// </ul>
+```
+
+### Comments
+
+You can add comments to your templates with the following syntax:
+
+```js
+{{! This is a comment }}
+```
+
+You can also use real html comments if you want them to end up in the output.
+
+```html
+<div>
+    {{! This comment will not end up in the output }}
+    <!-- This comment will show up in the output -->
+</div>
+```
+
+
+Precompiling Templates
+----------------------
+
+Handlebars allows templates to be precompiled and included as javascript
+code rather than the handlebars template allowing for faster startup time.
+
+### Installation
+The precompiler script may be installed via npm using the `npm install -g handlebars`
+command.
+
+### Usage
+
+<pre>
+Precompile handlebar templates.
+Usage: handlebars template...
+
+Options:
+  -f, --output     Output File                                                           [string]
+  -k, --known      Known helpers                                                         [string]
+  -o, --knownOnly  Known helpers only                                                    [boolean]
+  -m, --min        Minimize output                                                       [boolean]
+  -s, --simple     Output template function only.                                        [boolean]
+  -r, --root       Template root. Base value that will be stripped from template names.  [string]
+</pre>
+
+If using the precompiler's normal mode, the resulting templates will be stored
+to the `Handlebars.templates` object using the relative template name sans the
+extension. These templates may be executed in the same manner as templates.
+
+If using the simple mode the precompiler will generate a single javascript method.
+To execute this method it must be passed to the using the `Handlebars.template`
+method and the resulting object may be as normal.
+
+### Optimizations
+
+- Rather than using the full _handlebars.js_ library, implementations that
+  do not need to compile templates at runtime may include _handlebars.runtime.js_
+  whose min+gzip size is approximately 1k.
+- If a helper is known to exist in the target environment they may be defined
+  using the `--known name` argument may be used to optimize accesses to these
+  helpers for size and speed.
+- When all helpers are known in advance the `--knownOnly` argument may be used
+  to optimize all block helper references.
+
+
+Performance
+-----------
+
+In a rough performance test, precompiled Handlebars.js templates (in the original version of Handlebars.js) rendered in about half the time of Mustache templates. It would be a shame if it were any other way, since they were precompiled, but the difference in architecture does have some big performance advantages. Justin Marney, a.k.a. [gotascii](http://github.com/gotascii), confirmed that with an [independent test](http://sorescode.com/2010/09/12/benchmarks.html). The rewritten Handlebars (current version) is faster than the old version, and we will have some benchmarks in the near future.
+
+
+Building
+--------
+
+To build handlebars, just run `rake release`, and you will get two files
+in the `dist` directory.
+
+
+Upgrading
+---------
+
+When upgrading from the Handlebars 0.9 series, be aware that the
+signature for passing custom helpers or partials to templates has
+changed.
+
+Instead of:
+
+```js
+template(context, helpers, partials, [data])
+```
+
+Use:
+
+```js
+template(context, {helpers: helpers, partials: partials, data: data})
+```
+
+Known Issues
+------------
+* Handlebars.js can be cryptic when there's an error while rendering.
+
+Handlebars in the Wild
+-----------------
+* [jblotus](http://github.com/jblotus) created [http://tryhandlebarsjs.com](http://tryhandlebarsjs.com) for anyone who would
+like to try out Handlebars.js in their browser.
+* Don Park wrote an Express.js view engine adapter for Handlebars.js called [hbs](http://github.com/donpark/hbs).
+* [sammy.js](http://github.com/quirkey/sammy) by Aaron Quint, a.k.a. quirkey, supports Handlebars.js as one of its template plugins.
+* [SproutCore](http://www.sproutcore.com) uses Handlebars.js as its main templating engine, extending it with automatic data binding support.
+* [Ember.js](http://www.emberjs.com) makes Handlebars.js the primary way to structure your views, also with automatic data binding support.
+* Les Hill (@leshill) wrote a Rails Asset Pipeline gem named [handlebars_assets](http://github.com/leshill/handlebars_assets).
+
+Helping Out
+-----------
+To build Handlebars.js you'll need a few things installed.
+
+* Node.js
+* Jison, for building the compiler - `npm install jison`
+* Ruby
+* therubyracer, for running tests - `gem install therubyracer`
+* rspec, for running tests - `gem install rspec`
+
+There's a Gemfile in the repo, so you can run `bundle` to install rspec and therubyracer if you've got bundler installed.
+
+To build Handlebars.js from scratch, you'll want to run `rake compile` in the root of the project. That will build Handlebars and output the results to the dist/ folder. To run tests, run `rake spec`. You can also run our set of benchmarks with `rake bench`.
+
+If you notice any problems, please report them to the GitHub issue tracker at [http://github.com/wycats/handlebars.js/issues](http://github.com/wycats/handlebars.js/issues). Feel free to contact commondream or wycats through GitHub with any other questions or feature requests. To submit changes fork the project and send a pull request.
+
+License
+-------
+Handlebars.js is released under the MIT license.