backbone-events

Can anyone please explain me what delegateEvents in backbone.js does? The documentation did not help me to understand. My exact use case is: I have a main view X with an inner view Y. They work great, but if I go to main view Z and then go back to X (reusing, not recreating) then events attached to Y child elements get lost. delegateEvents solves this but I want to understand why. Essentially, when you call .remove() it is a proxy to the jQuery remove function, which removes the element from the DOM, as well as all associated events from the event hash that were bound to the element. Backbone

I'm trying to capture the scroll event within a Backbone.Marionette.CompositeView, but without success. As an exercise, I'm rewriting http://www.atinux.fr/backbone-books/ using Backbone.Marionette. As you can see, when you scroll down, more books are fetched and displayed (i.e. infinite scroll). However, I'm unable to capture the scroll event on my view. Here's my (simplified) code: LibraryView = Backbone.Marionette.CompositeView.extend({ // properties, initializer, etc. events: { 'scroll': 'loadMoreBooks', 'click': 'loadMoreBooks' }, // some functions loadMoreBooks: function(){ console.log(

I have a Backbone app that uses nested collections (at least that's how I think they're called). In my particular case there are tabs and subtabs , and each tab (model) contains a collection of subtab (model). For those who're more familiar with code, I'll write bellow my models and collections, and how subtabs are nested inside the tab model: // Subtab Model var Subtab = Backbone.Model.extend({ defaults: { label: undefined } }); // Subtabs Collection var Subtabs = Backbone.Collection.extend({ model: Subtab }); // Tab Model var Tab = Backbone.Model.extend({ defaults: { label: undefined,

I'm working on a application which has sidebar on the right side. That displays collection. Each model of the collection has select behavior. In the top center of the page I have one independant backbone view which acts like "info bar" and this view should update it's infomation when I select one of the views in the sidebar How can I do it? I think that the each view in the sidebar should have "selected" event with model argument, and my question is how can I listen that change in my info bar view in Backbone.js??? This sounds like something that would be served well by an event aggregator

I'm using the following code to create the view: LoginForm = Backbone.View.extend({ tagName :"form" ,id : "login-form" ,className :"navbar-form" ,initialize: function () { this.model = new StackMob.User(); this.render(); } ,render: function () { $(this.el).html(this.template()); return this; } ,events : { "change" : "change" ,"submit #login-form" : "login" } ,login : function( event) { event.preventDefault(); var self = this; this.model.login(true, { success: function( model) { app.alertSuccess( "User logged in"); self.render(); } ,error: function( model, response) { app.alertError("Could not

I'm beginning with Backbone.js and trying to build my first sample app - shopping list. My problem is when I fetch collection of items, reset event isn't probably fired, so my render method isn't called. Model: Item = Backbone.Model.extend({ urlRoot : '/api/items', defaults : { id : null, title : null, quantity : 0, quantityType : null, enabled : true } }); Collection: ShoppingList = Backbone.Collection.extend({ model : Item, url : '/api/items' }); List view: ShoppingListView = Backbone.View.extend({ el : jQuery('#shopping-list'), initialize : function () { this.listenTo(this.model, 'reset',

I want to have bookmarkable URLs that the browser can capture and handle. If I just use Backbone.history.start() , then I can use hash URLs, like /#accounts . But I want URLs without the hashes, a la /accounts . But I can't get this to work using Backbone.history.start( { pushState: true } ) ( as others have described it ). My routes are straightforward, and taken directly from the documentation . MyRouter = Backbone.Router.extend({ routes: { '/accounts': 'accounts', } }); I'm using Chrome (also tried with FF), and the behaviour is that an /accounts request goes straight to the server. Not