Reply 20 of 24, by kevodwyer
Introduced some html5 buzzword compliance. In a nice piece of irony, adding supposedly experimental html5 tech actually improved browser compatibility. I don't have any benchmark figures, but the changes have had a slight performance improvement. Memory usage has dropped considerably. Chrome still recommended (it now runs in firefox - but only just).
Added:
- the option to offload scaling to a CSS transform (although it does give everything a slightly 'glazed' look).
- the option of WebGL rendering. Have never programmed GL stuff before, so i'm reasonably surprised it worked at all.
- now using TypedArrays for memory, disk, screen & sound buffers. A nice feature is the ability to map multiple different arrays on top of the same source array. This made it possible to streamline emulated memory access.
As it turns out there was a better way for handling audio output. Now using the WebAudio API. Also added Adlib and GameBlaster cards - almost completely untested however.