Form CRUD with Batman.js and Rails 3.2
Ruby CoffeeScript
Latest commit 590e651 Feb 11, 2013 @zhubert Merge pull request #1 from jasonlaxdal/master
I updated the Gemfile for your Batman CRUD repo
Failed to load latest commit information.
app updated pagination May 22, 2012
config updated pagination May 22, 2012
db paginate results on a show page May 15, 2012
doc init May 7, 2012
lib init May 7, 2012
log init May 7, 2012
public init May 7, 2012
script init May 7, 2012
test switched to ams, added association includes May 9, 2012
vendor init May 7, 2012
.rvmrc init May 7, 2012
Gemfile Revised active_model_serializers gem repo path to current. Feb 11, 2013
Gemfile.lock Revised active_model_serializers gem repo path to current. Feb 11, 2013
Rakefile init May 7, 2012 init May 7, 2012

Batman Rails Demo

Using Batman.js, evaluate the following:

  • Simple form CRUD
  • Routing of resources - nested, with nav, pagination
  • Associations - has_many, belongs_to
  • Rails idiom and integration - shouldn't be an impedance mismatch
  • Data binding - views change automatically when data does
  • View Composition - weak, strong...just get it done
  • No Framework Poison Pills - that would be bugs and things that would jeopardize a production app
  • HAML/Coffeescript Friendly

Implementation Notes:

  • Serialization of JSON is done via Active_Model_Serializers. Currently requires a "scope" (that is, current_user-like object), hence the anemic user inclusion.
  • Rails 3-style Responders don't play well with Batman validation (usually doesn't matter since you would have client side validators too), note the server-side controller implementation. Pagination also needed some changes in the controller.
  • Packaging of views for prod as per Rigel Group


  • Batman makes a strong bid for "Client-side Rails" in my book. It was very easy to use, no rabbit holes, easy to debug, MVC that a Rails developer would recognize.
  • Delivered all the requirements above.