Recently, I was working on fixing some tinyMCE issues dealing with loading a rich text editor via Ajax. The issues with tinyMCE had to do with the larger problem of loading dynamic content after the page has loaded. There are often times where some sort of control or widget requires some core additions to the environment created by a page load. The essence of the issue is that when the script tries to access elements on the page, they may or may not be completely loaded.

This is an essential facet of Javascript that has brought about Ajax. This asynchronous nature has made dealing with page loading and understanding of the DOM much more critical. Specifically, this document load has been progressively getting solved in a reliable cross browser fashion. Just as libraries such as Prototype, jQuery, Dojo, YUI, etc. have done wonders for working with the DOM, the document onload has gotten some help. 

Dean Edwards made the original effort to provide an all encompassing solution for knowing when the DOM was loaded. This was later updated with input by John Resig, the lead jQuery creator. These helpful articles describe the problem and describe their solutions. Both Dean Edwards and John Resig have many good articles describing helpful best practices for Javascript to help ensure compatibility and interoperability. 

John Resig gave a presentation at google that provides an excellent primer into how jQuery was written and compares its tenants to that of Prototype and MochiKit. One point he makes is the use of namespaces to avoid conflicts with other libraries and to enable easier browser enhancements.

Tying this together, what I think would be beneficial is to implement a BSG namespace of library functions that gets loaded on the window.load. This would enable us to be more confident in how our functions are called and used. Specifically, in the case of tinyMCE, we would have the opportunity to test our code in something of a sandbox knowing that the DOM is fully loaded and there is little chance for a name collision. This also could be beneficial in regard to more organized Javascript as we could make an effort to keep code organized according to its template and/or partial.