Design Element
Comment on "Separation of Model and View Web Frameworks"
by Scott Stevenson — Aug 02
@omygawshkenas: and fires off a notification (Cocoa-style) for any listening javascript views to update themselves

As far as I can tell, SproutCore thankfully has this part covered.

@Tammer Saleh: We essentially wanted to be able to use our ActiveRecord models in the clientside code. To that end, we wrote Jester.

Jester looks pretty interesting and I think it's probably the right direction in the long term for Rails projects. It's hard for me to evaluate at this point, though, because I'm not sure how all the pieces fit together. I'm sure it would be more obvious to me from the overview example if I was a Rails expert.

Although syntactically I think this is the right direction and that you guys have done some good work, my overall goal here is to find one complete package so I don't have to assemble them by hand. In other words, I think something like this needs to be integrated directly into Rails and managed under the same folks with the same coding standards and release schedule. This is just my opinion.

@David Phillip Oster: The obvious answer is: just write the apps in Cocoa

I'd love to do that, but it's completely impractical in this case. The audience is not nearly predictable enough. Although maybe your suggestion was to build a working model since I said "prototype". I may have not phrased that well. It's probably more accurate to say my task is to build a initial version.

@Simon Richardson: I have to agree that a server side glue needs be written, but there is a better alternative to Jaxxer and that's Helma

I took a look at the site. It seems to be written in Java with a JavaScript syntax laid on top. For my purposes, I don't want to use a Java solution.
Back to "Separation of Model and View Web Frameworks"
Design Element

Copyright © Scott Stevenson 2004-2015