I have a render method in Backbone that goes basically like this:
render: function () {
$.tmpl(this.template, attrs).appendTo(this.el);
return this;
},
which is called from a router action:
action: function () {
$('#container').empty();
$('#container').append(myView.render().el);
},
Now, I want to apply a plugin on label
elements inside this view. My first thought was to call the plugin inside render
:
render: function () {
$.tmpl(this.template, attrs).appendTo(this.el);
this.$('label').inFieldLabels();
return this;
},
but this doesn't work (I'm assuming this is because the element hasn't been added to the DOM yet). It does work if I call the plugin in the router action though:
action: function () {
$('#container').empty();
$('#container').append(myView.render().el);
myView.$('label').inFieldLabels();
},
I'd rather not do this, because the plugin is part of the view, not the router, so it doesn't make sense to be calling it inside the action. Is there a better way to do this?
I was facing a similar issue but in my case even the above solutions wouldn't work because the parent views hadn't been added to the DOM yet.
Sticking with the convention of having the parent view add the children to the DOM, doing loadPlugins() in the render method didn't work.
This is what I did. It feels kind of hacky but could help, depending on how you're managing your views throughout the hierarchy:
Using a setTimeout of 0 allows the current call stack to finish, so by the time the timeout function gets called the view and all it's parents have been added to the DOM. (If you stick to the convention mentioned above).
Beter do it this way:
I was able to get this to work for my jQuery plugin only by specifying the context for jQuery in the render function:
I ran into a similar issue setting up the jQuery Tools Tooltip plugin. But I had a much different approach that works well: triggering a custom event on the view. As far as I know, there is no 'inserted into dom' event fired built into Backbone, so I just did it myself. I don't use a Router but the modified code above would look something like this:
I suppose the advantage is that the view stays ignorant of its container. The disadvantage is that it's like an extra line or two of code. But if you need to setup a lot of plugins or do more stuff that requires the element to be in the DOM, it will work well (and it keeps logic separated).
I actually like @Skilldrick's method of passing the container to the view, but I still feel as if it makes sense to have the parent view be responsible for inserting the children. I'm new to Backbone so please feel free to comment.
I've 'solved' this problem by adding a
loadPlugins
method to my view, so I can domyView.loadPlugins()
after rendering in the action. It's not ideal, but it works.Edit: Well, I've heard from the horse's mouth and it looks like I can't apply the plugin before the element's been added to the DOM, so either I can do as above (with
loadPlugins
) or I can modify the code so the element gets added to the DOM in therender
method. Hope this helps someone in a similar position.Here's how I'm doing it now: