I had an ‘iframe’ parallel loading implementation but it’s not working for the damn IE, so not usable on more than the 60% of browsers around

Your solution is quite appealing since it seems easy to implement on most sites and working cross-browser. My compliments.

we’d have to let the user be able to specify some sort of “test” function for a script, which if it fails (with a try/catch), then it assumes the script failed and so it moves on to the next fallback.

i explored the idea in LABjs but came to the conclusion that it was a corner case that would increase the size and complexity of LABjs more than the benefit, at least in terms of having it in the core library that is included on every site, as only some people would feel that was a necessary functionality.

However, I *do* feel like this is a perfect example of something that should be an “add-on” to LABjs. In the same way that I did fLABjs as an adapter add-on for file:/// usage of LABjs (local filesystem loading for development environments), this same type of thing could be layered on top of LABjs actually quite easily.

I have wanted to build core functionality into LABjs that can be used as the nuts and bolts of larger more complex dependency systems and things. This would be a perfect test case for that kind of concept. Basically, you could create a simple wrapper to LABjs that does exactly what you’re suggesting… it might look something like this:

function loadOrFallback(scripts,idx) {
   if (idx == null) idx = 0;
   $LAB.script(scripts[i].src).wait(function(){
      try { scripts[idx].test(); } catch(err) {
         if (idx < scripts.length-1) loadOrFallback(scripts,idx+1);
      }
   });
}

function test_jQuery() { jQuery(""); }

loadOrFallback([
{src:"http://some.tld/framework.js",test:test_jQuery},
{src:"http://another.tld/framework.js",test:test_jQuery},
{src:"framework.js",test:test_jQuery}
]);

The "loadOrFallback" function tries the first script passed in, and then does a wait() function which runs the "test" function you pass in once that script either loads or fails. if the try/catch of the "test" function throws an error, a recursion back into "loadOrFallback" is done, with the next index of the scripts to load/test. So, this should cascade through the scripts you pass in, trying to load each one, one at a time, and test if it loaded correctly. If not, it should try the next one.

You could do a simple function like that, or you could write a wrapper similar to fLABjs that gives a chaining API compatible with (but augmented) LABjs, and then load both core LABjs and then this other wrapper on top of it.

If I experiment with the full wrapper option and get something tangible, I'll obviously do a blog post about it, so keep an eye out. ]]>