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
😀
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:
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:
😀