-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change the way ROMs are loaded #3
Comments
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? |
...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... |
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 |
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. |
Hi,
I'm wondering if we could save bytes by changing the way ROMs are loaded:
@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?
The text was updated successfully, but these errors were encountered: