//You have to scroll down to the bottom of the function definition
//before being able to tell if Connector is the function or its result
var Connector = function() {
…
}();

//Here the parens make it more obvious that it’s not just a simple
//assignment of a function
var Connector = (function() {
…
})();

It’s identical in meaning, but the parens convey pretty clearly that something is going on. I’ve seen this style a few places and it seems as though this is becoming the suggested coding style.

Regarding adding this to the populateExtendedContent() call, this will not work. I think this is where this method of creating objects differs from normal OO programming, since this refers to the object that is being returned by the function. The private methods and variables are outside of the scope of this when in the Connector.

I do like your idea of following common programming standards and prefixing the private variables and methods with underscores. I have updated the code to do this.

I have been trying out RightJS (rightjs.org), which uses a Class object whereby you can create classes and extend those to other classes, and it also has the ability to encapsulate an Options class which provides a uniform way to pass options to your objects. I kind of like this way a little better because it is a little simpler.

The line number you reference are off by one.

Also, in line 38, could you use this.populateExtendedContent() (add the keyword “this”)? Do you have a preference on using “this” to indicate that it is a method of this object? And what about prefixing the private methods with an underscore? That might reduce maintenance headaches later on to help keep it straight which are public and private methods.