Ruby on Rails

On Tue, Apr 2, 2013 at 8:43 AM, Johan Vauhkonen
<johan.vauhkonen@gmail.com> 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 application?
>
> Should I be using the asset pipeline? Or should all client side stuff be
> separated from Rails?
>
> I'll be creating a simulation engine for this application to simulate
> results that the application will show.
> Using Rails I thought I'd make the simulation engine a Rails Engine to
> separate the logic from the rest of the application.
> Is that a good idea? Can the Rails API gem make use of engines?

A colleague and I were having a very similar discussion today. He
allowed as he just wrote his own asset pipeline, combining together
all the various compilers and converters and such into something
pretty simple that he's using under Sinatra. He had said he initially
thought about using Rails minimally for the asset pipeline, but then
came up with this.

--
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+unsubscribe@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.