A bit of an obscure question, but I'll ask it here in case anyone else is doing obscure stuff.
I'm trying to integrate a JS library into Quest (one of mine, just for fun, to see if I can), and the code uses $.ajax to load files. However, when I provide the "GetFileURL" url to that API, I get an error like this:
XMLHttpRequest cannot load quest://local/helloworld.txt?_=1453648271432. Cross origin requests are only supported for protocol schemes: http, data, chrome-devtools, chrome, https.
I had this problem with Chrome before, and I had to resort to using a local (node) web server to give it a URL it would be able to load from. I hadn't expected to see this with Quest. And using a web server won't work, as Quest is serving files itself.
Is there a better URL to use to access local files from a JS Ajax call if the normal "quest://" ones don't work? Or is it just hopeless?
Ideally I'd like to be able to load files on demand from the JS code, as one file can "include" another, and the code needs to be able to resolve those references itself without having to go back to the Quest ASLX file to load the data.
If there is no other solution, I'll have to resort to something less ideal, but let's shoot for ideal first.