Design Element
Comment on "Separation of Model and View Web Frameworks"
by Tammer Saleh — Aug 02
We hit the same problem you're describing while developing one of our Rails applications. We essentially wanted to be able to use our ActiveRecord models in the clientside code. To that end, we wrote Jester. Jester "mirrors" your models in the same way that ActiveResource does - by interacting with your RESTful controllers. This allows you to do things like "User.find('first', {name: 'billy'})" or "" on the client side.
Back to "Separation of Model and View Web Frameworks"
Design Element

Copyright © Scott Stevenson 2004-2015