4 ms·
Semi-related question for you experts out there: how do these frameworks fit into a multi-page web app (ie: a typical Rails app)? They all seem to target the si
by cmer 14y ago
Semi-related question for you experts out there: how do these frameworks fit into a multi-page web app (ie: a typical Rails app)? They all seem to target the single-app market and the examples are always so simple that I have yet to figure how to build a larger application with either Backbone, Spine or Ember.
Is the idea to treat each page as a unique application?
- dclaysmith 14y agoIn backbone, I will create a new Router for each page (though sometimes you might reuse the same router for groups of pages that contain the same views).
- cmer 14y agoThanks! I'll give that a try.
- hehejubee 14y agoWhere a typical Rails app has a controller per model with all the crud actions for that model, we have used one Backbone router per model. It worked out so that there was one Backbone router per top level nav item.
- apsurd 14y agoFor multi-page applications the problem becomes how to load and manage dependencies on the client-side. I use http://requirejs.org/ http://requirejs.org/ for this.