7 ms·
Hmmm. Any reason all the views and models are attached to the window object instead of namespaced under some kind of app controller?
by dts 15y ago
Hmmm. Any reason all the views and models are attached to the window object instead of namespaced under some kind of app controller?
- tbranyen 15y agoThere are a number of issues with the project, but I'm assuming it was created this way to be easier to digest for newcomers.
- smcguinness 15y agoWould you point out a few of them if you don't mind?
- danso 15y agoYeah, as a newcomer to Backbone, this has always been something that's thrown me off, including in the otherwise excellent Todo example: http://documentcloud.github.com/backbone/docs/todos.html http://documentcloud.github.com/backbone/docs/todos.html The backbone boilerplate on Github (by tbranyen) has been a useful model to follow: https://github.com/tbranyen/backbone-boilerplate/blob/master/app/namespace.js https://github.com/tbranyen/backbone-boilerplate/blob/master...
- VMG 15y agoDocumentCloud (by the creator of Backbone) is also using window-bound variables. Seems to work for them I suppose.
- jashkenas 15y agoYes, when you're in control of the page, it's nice to be able to have different parts of your app ready-to-hand. In our case, that means Documents, Notes, Projects, Accounts, Organizations, and so on... If your "app" is going to be embedded as a part of someone else's page, then you have to be much more careful. The results cards in the sidebar here are only exposed through a single variable: "eg2012.Card": http://www.nytimes.com/2012/02/08/us/politics/minnesota-colorado-missouri-caucuses.html http://www.nytimes.com/2012/02/08/us/politics/minnesota-colo...