{"id":1706,"date":"2019-02-23T01:24:20","date_gmt":"2019-02-23T00:24:20","guid":{"rendered":"https:\/\/mehm.net\/blog\/?p=1706"},"modified":"2019-02-23T01:24:20","modified_gmt":"2019-02-23T00:24:20","slug":"porting-tads-to-the-browser","status":"publish","type":"post","link":"https:\/\/mehm.net\/blog\/?p=1706","title":{"rendered":"Porting TADS to the browser"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n

This is one of my most recent projects (at least those that I get around to writing about…). I recently got infatuated again with Interactive Fiction, played through Ballyhoo<\/a> by Infocom as well as took part in the judging of the Interactive Fiction Competition<\/a>. In the course of this, I became more interested in how these games are made and am still blown away by how good results they were able to achieve back then (Google Asssistant and Alexa have nothing on those old interpreters apart from their voice recognition). <\/p>\n\n\n\n

This lead me to playing around with the Text Adventure Development System (TADS)<\/a> by Michael J. Roberts. TADS is one of the best-known toolkits to create interactive fiction and probably shares the top one spot with Inform<\/a>.<\/p>\n\n\n\n

Apart from starting to build a small game, I noticed that it doesn’t have a real native browser port. And I had never worked with emscripten<\/a> before, so this seemed like a good opportunity. Emscripten is a cross-compiler which can compile C++ to javascript in order to run it in a browser, for example.<\/p>\n\n\n\n

Process<\/strong>
<\/p>\n\n\n\n

In order to run TADS games, I looked at the available source code for TADS interpreters. TADS itself offers the code for the interpreter (see https:\/\/www.tads.org\/t3dl\/t3_src.zip<\/a>), but to get the job done it was easier to look for a whole package in which everything required (handling the terminal, loading files, …), which I found with FrobTADS<\/a>.<\/p>\n\n\n\n

The next step was to find a compatible curses<\/a> library in order to render the text to the browser. After some testing, I found PDCurses<\/a> which comes with SDL1 and 2 backends, which in turn makes porting them using emscripten easy as SDL is one of the libraries that emscripten ships with.<\/p>\n\n\n\n

In order to make both packages work, I had to make a few changes because clang, on which emscripten is built, was complaining about a few things in the code. Also the autoconf configuration couldn’t figure out that a curses library was present so I had to hardcode it in there.<\/p>\n\n\n\n

One tricky thing was that emscripten complained about SDL_Delay being called, which will make the runtime stop. SDL_Delay is used inside PDCurses and then in turn used by FrobTADS as an implementation to pause the program. I solved this by using the Emterpreter<\/a>, but I think that a cleaner solution would be to use emscripten_sleep()<\/a> instead.<\/p>\n\n\n\n

Result<\/strong><\/p>\n\n\n\n

You can find my fork of FrobTADS over on github: https:\/\/github.com\/SpookyFM\/frobtads<\/a>. I added a fork of PDCurses as a submodule for convenience. This includes the shell (hardcoded to run the demo game) as well as the changes I made.<\/p>\n\n\n\n

In order to build the whole thing, do the following steps:<\/p>\n\n\n\n

For setting up your build environment: <\/em>
source .\/emsdk_env.sh
To configure and build FrobTADS:<\/em>
emconfigure .\/configure CPPFLAGS=\"-I\/PATH\/TO\/PDCurses-3.6\"
emmake make

To build PDCurses, run inside PDCurses\/sdl1:<\/em>
emmake make

To build everything (Should have a .gam file in there as well):<\/em>
emcc frob.bc \/PATH\/TO\/frobtads-1.2.3\/PDCurses-3.6\/sdl1\/libpdcurses.a -o new.html --preload-file pdcicon.bmp --preload-file pdcfont.bmp --preload-file *.gam --use-preload-plugins --shell-file shell.html -s EMTERPRETIFY=1 -s EMTERPRETIFY_ASYNC=1
<\/pre>\n\n\n\n
To demonstrate the result, I have used the first winner of the Interactive Fiction award, Uncle Zebulon’s Will<\/a> by Magnus Olsson. You can find the game playable in the browser here<\/a>. Note that the download is actually quite heavy, for a text adventure, so give it a moment.<\/p>\n\n\n\n
Possible next steps<\/strong><\/p>\n\n\n\n
At the current moment, this is more of a proof of concept than something ready to use. The above-mentioned SDL_sleep is one of the things that should be easy. Other things include:<\/p>\n\n\n\n