Emglken: Difference between revisions
(Created page with "'''Emglken''' is a project by Dannii Willis which compiles several interpreters with [https://emscripten.org/ Emscripten] into Javascript and WebAssembly, so that the inte...") |
No edit summary |
||
Line 8: | Line 8: | ||
Emglken is available as a console app via npm, as well as being bundled into [[Lectrote]] and [[Parchment]]. | Emglken is available as a console app via npm, as well as being bundled into [[Lectrote]] and [[Parchment]]. | ||
[[Category:Interpreter]] |
Revision as of 01:18, 20 January 2022
Emglken is a project by Dannii Willis which compiles several interpreters with Emscripten into Javascript and WebAssembly, so that the interpreters can be played anywhere with a modern Javascript runtime, such as any modern web browser.
From the readme:
Over the years many Interactive Fiction interpreters have been written which use the Glk API, or have been adapted to do so. Emglken takes some of these interpreters, compiles them to use the RemGlk Glk library using Emscripten, and then outputs to Javascript and WebAssembly. These interpreters, which once needed to be compiled for each distinct operating system and CPU combination, can now be run anywhere there's a modern Javascript runtime: on the web with Parchment, in desktop apps like Lectrote, or in Node.js directly.
Emglken itself doesn't have a lot of code, RemGlk does most of the work for us. What Emglken does provide is a virtual file system for Emscripten which lets RemGlk think it is running on a normal Linux filesystem, but is actually transformed to use GlkOte's Dialog API. Emglken also provides a common interpreter interface to handle setting up the connections between each interpreter and GlkOte.
Emglken is available as a console app via npm, as well as being bundled into Lectrote and Parchment.