Yes, that is how I was thinking.

When the document was written we had not broken out the DNN specific portions of the ClientAPI from the "generic use in any project" portions.  This explains why the doc is not quite right, and the need for a different namespace (DNNClientAPI).   Sorry for the confusion.

Hi ccarns

I believe that was jon's point. The onload event may be used by other modules or the DNN core. The method mention allows you to add multiple onload events.

you will find the onload function that i showed before will only fire the last onload function that was loaded on the page, as my modules are used for work i'm not going to rush and change them, but for future reference i'm definitely going to look closer at the ClientAPIs.

cheers