What I’m trying to do is dynamically include one or more js files from within Javascript. I know there are a bunch of techniques for this, but I’m looking for a solution that follows these rules:
1) Not use any JS frameworks or libraries (jQuery, Prototype, etc).
2) The script should halt execution until the external js file is completely loaded and parsed by the browser.
The rational behind #2 is the external js file will include function definitions that need to be used immediately after the script is included. Most of the time the browser hasn’t had time to parse the js file before I start calling those functions.
I don’t mind using a callback to know when the script is finished loading, but:
1) I don’t know ahead of time how many scripts are going to be dynamically included, so I don’t want and can’t write a bunch of nested callbacks. I just need to know when they’re all finished loading.
2) I’m wording that trying to use some kind of “load” event to fire the callback might not work if the browser has cached the JavaScript.
Edit I should have mentioned from the start that this is for a plugin system, but I wanted to keep my question/answer generic enough to be helpful to other people.
Users would define which plugins they want to load in an array.
plugins = [ 'FooPlugin', 'BarPlugin' ];
I would then loop through the array, and load the js script for each plugin:
for(var i = 0; i < plugins.length; i++) {
loadScript('plugins/' + plugins[i] + '.js');
}
Each plugin pushes itself onto the loaded_plugins array (This is an example of FooPlugin.js)
load_plugins.push({
name: 'FooPlugin',
// Other plugin methods and properties here
});
Works cross browser, starting with IE6.
Minified / obfuscated:
Quick explanation of the branches:
If the script tag calling loadScript is within the document head or body, document.body will be undefined, as the DOM isn’t in yet. As such, we can’t use the standards method of appending a tag, and we must use doc write. This has the advantage that the tags we write will happen in necessarily sequential order, but the disadvantage that we must have a global scope callback function.
Meanwhile, if we have document.body, we’re golden for Doing It Right (-ish – we make sacrifices when there’s no libraries around to help do it right-er, hence the .onload(). Still, it’s not like we’re about to throw lots of events on a script tag, so it’ll probably be OK.) The disadvantage (maybe?) is that the scripts all load asynchronously, so we need to have a countdown run as they load.