How should I name my javascript library functions so they are differentiable from plain old javascript?

Question

I am writing a custom UI builder in js. It uses an implementation of a factory to build elements. To make sure that it was obvious which functions were part of the library versus which were part of plain old javascript I used a naming convention of function _FunctionName(). However, I find it tedious to always be doing Factory._FunctionName().

Should I just remove the naming convention (function FunctionName())or stick to it?

Are there naming convention common / best practices with regards to making libraries like this?

edit:

var __PanelFactory = function () {
 //"private"
 var Panels = [];
 //exposed
 function _GetPanel(id) {
  //etc
 }
 return {
    _GetPanel: _GetPanel,
 };
};

var Factory = new __PanelFactory();
Factory. //this will show certain plain javascript functions 
         //like toString, constructor, hasOwnProperty, isPrototypeOf, etc...

//note that even jQuery can have the previous list used with something like
$(selector).

//So to differentiate I made sure my functions start with _
Factory._GetPanel(1);

//Should I just make it easy on myself and allow
Factory.GetPanel(1);

//Or is there value in leaving the naming convention in?

Answer 1

Here are some pretty common conventions in javascript.

Constants

Usually in ALL_CAPS_WITH_UNDERSCORES

var MAX_COUNT = 100;
var BASE_URL = "http://example.com/api/";

Variables

Usually in lowerCamelCase

var currentCount = 0;
var userName = "timrwood";

Constructors

Usually in UpperCamelCase

function Factory(){}
var factory = new Factory();

Methods

Usually in lowerCamelCase

Factory.prototype.getPanel = function(){};
var factory = new Factory();
var panel = factory.getPanel();

Private Variables/Methods

Usually in _lowerCamelCaseWithAUnderscorePrefix;

Factory.prototype._fetchPanel = function(){};
Factory.prototype.getPanel = function() {
    return this._fetchPanel();
}

Answer 2

There is a question already on SO that links to a good document on Javscript coding conventions (including naming):

• javascript naming conventions
• http://javascript.crockford.com/code.html

The key bits you've asked about:

• Use namespaces (with inital-caps names).

This is somewhat optional, as PanelFactory won't collide with plain Javascript. It might collide with other libraries if you are making a public API to be consumed by third parties, though:

var MyApp = MyApp || {};
MyApp.__PanelFactory = function () { // ...

• Get rid of the underscores (_) before all function names.

You don't need the underscores, as people who have been working with JavaScript for a while know the default instance-scoped functions built into every object (toString etc):

MyApp.PanelFactory = function () {
  // ...
  function GetPanel(id) {
    //etc
  }

• Name object constructor functions with initial-caps names, but name global or namespace-scoped functions and instance-scoped functions with initial-lower-case names:

This is just a standard convention. It doesn't help distinguish built-in functions, but as I said in the previous item, you don't need to.

MyApp.PanelFactory = function () {
  // ...
  function getPanel(id) {
    //etc
  }

• Name local variables with initial-lower-case names:

This will help you tell the difference between a namespace, an object constructor, and an instance of an object (where you would expect custom instance-scoped functions, commonly called "methods", to exist).

var factory = new MyApp.PanelFactory();
var panel = factory.getPanel();