Re: [Rails] Help with single page application structure

2013-04-05 Thread RonPhillips
This tut shows a combined approach: http://blog.berylliumwork.com/2012/09/tutorials-on-angularjs-and-rails-2.html?view=classic (Don't forget to download angular-resource and require it in application.js. Other than that, everything worked.) I'm fiddling with it right now, because I don't reall

Re: [Rails] Help with single page application structure

2013-04-05 Thread Johan Vauhkonen
Do you disable Rails routing somehow when using client-side routing? On Thursday, 4 April 2013 14:31:09 UTC+2, tamouse wrote: 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.

Re: [Rails] Help with single page application structure

2013-04-04 Thread Johan Vauhkonen
I've initially made a HomeController that serves the initial index view (with it set as the root in routes) but I think I like the /public way better. Thanks for the idea! On Thursday, 4 April 2013 14:31:09 UTC+2, tamouse wrote: Absolutely, you can go so far as to have your SPA initial downlo

Re: [Rails] Help with single page application structure

2013-04-04 Thread Walter Lee Davis
On Apr 4, 2013, at 8:31 AM, tamouse mailing lists wrote: > > On Apr 4, 2013 7:20 AM, "Johan Vauhkonen" 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? > > > >

Re: [Rails] Help with single page application structure

2013-04-04 Thread tamouse mailing lists
On Apr 4, 2013 7:20 AM, "Johan Vauhkonen" 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 ind

Re: [Rails] Help with single page application structure

2013-04-04 Thread Johan Vauhkonen
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? -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group a

Re: [Rails] Help with single page application structure

2013-04-04 Thread tamouse mailing lists
On Apr 4, 2013 1:35 AM, "Johan Vauhkonen" wrote: > > I think for me, using Sinatra would mean I'd have to write a lot of things that Rails bring which I don't want to Agreed; we were talking alternatives and for his needs, he really only needed the pipeline.I was just trying to illustrate that st

Re: [Rails] Help with single page application structure

2013-04-03 Thread Johan Vauhkonen
I think for me, using Sinatra would mean I'd have to write a lot of things that Rails bring which I don't want to. -- 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

Re: [Rails] Help with single page application structure

2013-04-03 Thread tamouse mailing lists
On Tue, Apr 2, 2013 at 8:43 AM, Johan Vauhkonen wrote: > I'm planning on creating a single page application using AngularJS on the > client side. > > I'm not sure if I should use Rails as it is, or the Rails API gem or some > other solution. > Anyone got any suggestions on how you structured your

[Rails] Help with single page application structure

2013-04-03 Thread Johan Vauhkonen
I'm planning on creating a single page application using AngularJS on the client side. I'm not sure if I should use Rails as it is, or the Rails API gem or some other solution. Anyone got any suggestions on how you structured your application? Should I be using the asset pipeline? Or should all