Split Loader to a new Repo

[explorigin]

Consider moving the loader to a new repository. Staying in this repo, it becomes the step-child because it's not included in the API documentation or the example. Furthermore, it's truly completely independent of Overture (other than the "O" namespace which can be optional).

While I imagine others would like to choose their own, more popular, loader, the Overture loader stands out in that it's great for mobile web applications because:

• it's probably the smallest dynamic loader out there
• it can cache to localStorage

The build steps for it aren't complicated and one could easily use gulp to package it up instead of transferring over the whole build chain of Overture.

All it needs is:

• package.json
• gulpfile.js
• Readme.md

😀

[neilj]

Yeh, there are quite a few Loader libs out there which are pretty decent. This one does exactly what we think it should do, but as you say it's entirely independent of Overture itself. The main reason it's in the same repo is because it was easier for us to manage than having lots of separate repos. We should look into splitting it out.