Change the way ROMs are loaded

[xem]

Hi,

I'm wondering if we could save bytes by changing the way ROMs are loaded:

• Keep AJAX but without the arrayBuffer option so it can be synchronous
• Provide the ROMs content in base64 in the URL's hash instead of its path
• Use the file API to read the ROM's content (uploaded via a file uploader or by drag & dropping it from the file explorer to the browser...)

@aemkei @p01 @rlauck @subzey do you think one of these options could be a good alternative to the current ROM loader? ... Any idea on how to implement one of them?

[rlauck]

I've used the file api and drag+drop before and I dont think either would result in smaller code. base64 encoding in data uris would be a great way to go... could we also encode the 80 bytes of static font glyphs in there too?

[xem]

...we could, but these glyphs aren't really a part of the ROMs, they're more a part of the emulator. Or more specifically, a part of the emulator's BIOS. (its first reserved 512b)

I'll try the base64 thing then. or maybe I'll just use a string, instead base64...

[rlauck]

Fair enough, maybe we could encode the glyphs in a similar encoding and append it to the ROM before decoding? Not sure if it would help. With base64 we can rely on atob/btoa. I haven't had time to look at it today but I'll play with it tonight when I get a chance

[xem]

Hi, sorry, I just realized that the latest version of the emulator is buggy. For example, we can't move freely in BREAKOUT, the pixels keep being drawn if we release the keys in XMIRROR, etc.
We have to debug it or rollback to a previous version before trying to golf it better...=(