Delete me

and

events: { ”click a[data-action=delete]“: “delete”  }

This just makes more sense to me personally.

http://lostechies.com/derickbailey/2012/02/06/3-stages-of-a-backbone-applications-startup/

you should have an application object with an initialize or start method instead: 

http://lostechies.com/derickbailey/2011/08/30/dont-limit-your-backbone-apps-to-backbone-constructs/

Can I get you to post that code in to an issue on the Marionette project issue list: https://github.com/derickbailey/backbone.marionette/issues

A lot of people are having that problem these days, and getting that info out to everyone while I’m trying to find time to dig in and fix this, would be awesome :)

Here is the meat and potatoes:

Backbone.Marionette.TemplateCache.loadTemplate = function (templateId, callback) {
            var that = this;

            if (templateId && templateId.length) {

                var tmpId = templateId.replace(“#”, ”");
                var url = ”/templates/” + tmpId + ”.htm”;
                var promise = $.trafficCop(url);
                promise.done(function (templateHtml) {
                    var $template = $(templateHtml);
                    var template = that.compileTemplate($template.html());
                    callback(template);
                    App.vent.trigger(templateId + ”:loaded”); // necessary to load sub views in conjunction with ’NestedViewsApp.loadSubView’ method.
                });
            }
        }

        App.loadSubView = function (parentView, childView) {

            if (Backbone.Marionette.TemplateCache.templates[parentView.template]) {

                var $viewContainer = parentView.$el.find(parentView.subViewContainer);

                $viewContainer.html(childView.el);
            }
            else {
                NestedViewsApp.vent.bind(parentView.template + ”:loaded”, function () {

                    var $viewContainer = parentView.$el.find(parentView.subViewContainer);

                    $viewContainer.html(childView.el);
                });
            }
        }

And the call to loadSubView is within the parentView.render method as follows:

Parent.ParentView = Marionette.ItemView.extend({

                tagName: ”div”,
                className: ”parent-view”,
                template: ”#parent-view-template”,

                render: function () {

                    Marionette.ItemView.prototype.render.apply(this, arguments);

                    var childView = App.Children.getChildView();

                    App.loadSubView(this, childView);
                }
            });

BTW, this works well with Marionette.CompositeView as the childView, which rocks. If anyone can think of a more elegant way to handle this or provide any feedback, sharing is always appreciated.

Have a great Memorial Day weekend!

A lot of the things I might blog about aren’t necessarily software engineering topics.  I suspect it is because it is “more new” to me and therefore more interesting, but I might write more about life as an indie app developer.

One of these days I’ll take your advice and contribute in this way, Sharon.  I’ll make sure to give you credit on my blog once it crosses over from my dreams into our shared reality :)

I typically wrap all my code in an IEF, always, to avoid any pollution of the global space now or in future.