On Apr 4, 2013, at 8:31 AM, tamouse mailing lists wrote: > > On Apr 4, 2013 7:20 AM, "Johan Vauhkonen" <johan.vauhko...@gmail.com> wrote: > > > > Is it a viable alternative to separate client and back end? > > > > To have AngularJS take care of everything client side and Rails take care > > of only the back end? > > > > Absolutely, you can go so far as to have your SPA initial download be a > static index.HTML in ../public, and just have your routes speak JSON to the > Angular requests. I'm working on this currently only using backbone and > underscore.
There's a few Railscasts that cover Ember and Angular and they all start from this premise. You use Rails, but you don't do that much in it. It's just there providing the persistence, and all of your real work happens in the public folder. Walter -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-talk@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
