Quote from other thread moved over here.
You actually don't really need to optimize the .oam file as it gets unpacked and takes up some space on WordPress. But only the needed files are actually referenced in the rendered output.
I'd like an option that in it's simplest form allows to overwrite the location of the runtime for all uploaded widgets. This could be a folder on your own library or a CDN folder. Surly it doesn't override the version but you can change the folder containing runtimes. Also when unpacking... the runtimes in the .oam files could be all additional copied to a single folder on your wordpress installation. Potentially you accumulate all runtime versions of uploaded files and then could point all your widgets to that folder to load their respective runtime version. This would benefit sites with multiple widgets as they start profiting from cached calls.
Update:
I was just investigating this on a site and each runtime is referenced only once per version even though Hype widget specific instances are referenced. The HYPE_DocumentLoader (loadScriptIfNecessary) is seeming to look if the runtime version (string) is defined in the page (window) already and discards double request. Nice Job. So this feature request seams actually resolved. Correct me if I am wrong.
One thing to consider is that if you edit widgets over time is… you will have to render all widgets with the same Hype version and re-upload them all. Otherwise you will be accumulating around the full size (around 60-100) KB for each runtime version needed for older uploaded Hype .oam widgets. There is currently no way around this "bug" other then re-uploading all Hype .oam file after a fresh export (assuming that the most current runtime isn't always backwards compatible).