tentjs-rails 0.0.1 → 0.0.2

data/README.md

@@ -15,3 +15,49 @@ And then execute:
 Or install it yourself as:
 
     $ gem install tentjs-rails
+
+## Using Tent
+
+Rather than extending Backbone prototypes directly, Tent builds on top of them. That way, you can still create vanilla Backbone View, Models, and Collections without the additions that Tent provides. So, creating a view that uses Tent's extensions looks like this:
+
+```
+view = new Tent.View();
+```
+
+## Tent.View
+
+### Binding to an object
+
+By binding to an object using the `view.bindTo()` function, one can ensure that the binding is released when the view is closed using Tent's `view.close()` function.
+
+```
+view.bindTo(view.model, 'change', view.doSomething);
+```
+
+`bindTo` limits you to using the calling object as the context, which makes unbinding easier. If you must use another object as the context for a binding callback, use Backbone's `on` function.
+
+
+### Unbinding from an object
+
+Unbinding from an object is done with `unbindFrom`:
+
+```
+view.unbindFrom(view.model);
+```
+
+### Releasing all bindings
+
+When closing a view, Tent's `close` function takes care of releasing bindings made with `bindTo`, but the bindings can also all be released with `unbindAll`.
+
+```
+view.unbindAll();
+```
+
+### Closing a view
+
+Calling `view.close()` will do a fiew things:
+
+1. Call `view.beforeClose()` if it's been defined.
+2. Call `view.unbindAll()` to get rid of bindings.
+3. Call `view.off()` to get rid of DOM bindings.
+4. Call `view.remove()` to remove the view DOM element itself.

data/vendor/assets/javascripts/tent.view.js

@@ -5,7 +5,7 @@
 
       object.on(event, callback, this);
 
-      if (!_.contains(this._bindings)) {
+      if (!_.contains(this._bindings, object)) {
         this._bindings.push(object);
       }
     },

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: tentjs-rails
 version: !ruby/object:Gem::Version
-  version: 0.0.1
+  version: 0.0.2
   prerelease: 
 platform: ruby
 authors: