Loading external resources

[lptr]

Right now if a module wants to load external resources, it cannot reliable do that. There is a hack that you can write:

require("http://youtube.com/iframe_api", function { /* ... */ })

But doing so makes you implicitly rely on your module being packaged as AMD (i.e. that an async require() function is available in the context). Once you package the module in a Node JS app, it will break. There is already a plan to fix this, but we cannot do that until modules have a better way to access external resources: #122.

Proposal: add a function to the Spaghetti class (nee SpaghettiConfiguration, see #126), so modules can load resources like that. It should look something like this:

function getResource(url:String, onSuccess:Dynamic->Void, onError:Dynamic->Void = null);

[lptr]

The implementation of this function would be different for Require and Node JS packaging.

[lptr]

In single file applications we could throw a runtime error, or we could assume that the application will be run as Node, and just use Node's require().