Possible remote event binding for Entwine.js

gistfile1.js

/*
Old style. Problems: onmatch is slow. Leaks memory, because there's a reference from window to this node, and window exists forever, so that reference holds this DOM node out of the garbage once it's removed from the document.
*/

$('.node').entwine({
  
  onmatch: function(){
    var self = this;
    $(window).bind('load', function(){ self.initialise(); });
  },

  initialise: function(){
  }

});

/*
New method. Uses event delegation, so immediately active. By centralizing logic, hopefully eliminates memory leaks.
*/

$('.node').entwine({

  initialise: $.entwine.delegate(window, 'load', function(){
  }),

  myParentHasChanged: $.entwine.delegate(function(){ return this.parent(); }, 'change', function(){
  })

});

  

So I guess those object literal keys are just used to satisfy the JS spec, right?
Terms like 'initialise' could be quite misleading, devs could pick the up for usage elsewhere as normal functions, and wonder why they're never called.

Sort of. They're real functions, and can be overloaded, called with _super, etc. It's up to the dev to pick a good key that's explanatory & not confusing.