TADS 3 Library - console input/output manager
This module defines the low-level functions for handling input and output via the traditional interpreter's user interface, using the local keyboard and console via the "tads-io" function set.
The functions in this module are designed primarily for internal use within the library itself. Games should use the higher level objects and functions defined in input.t and output.t instead of directly calling the functions defined here. The reason for separating these functions is so that we can substitute the Web UI versions for games that wish to use the Web UI insetad of the traditional console UI.
Summary of Classes
Summary of Global Objects
Summary of Global Functions
Generate a string to show hyperlinked text. If we're not in HTML mode, we'll simply return the text without the hyperlink; otherwise, we'll return the text with a hyperlink to the given HREF.
If the display text is included, we'll generate the entire link, including the <A HREF> tag, the hyperlinked text contents, and the </A> end tag. If the text is omitted, we'll simply generate the <A HREF> tag itself, leaving it to the caller to display the text and the </A>.
The optional 'flags' is a combination of AHREF_xxx flags indicating any special properties of the hyperlink.
Generate a string to show hyperlinked text, with alternate text if we're not in HTML mode. If we're in HTML mode, we'll return linkedTxt linked to the given HREF; if we're in plain text mode, we'll return the alternate text as-is.
aioInputDialog (icon, prompt, buttons, defaultButton, cancelButton)
aioInputFile (prompt, dialogType, fileType, flags)
Show a file selector dialog
Cancel a suspended input line
Get a line of input from the keyboard, with timeout
Write text to the main game window
Set/remove the output logging file
Check to see if we're in HTML mode
Initialize the display. The library calls this at the start of the game, and after each RESTART, to set up the layout of the game window.
Initialize the user interface. The library calls this once at the start of the interpreter session to set up the UI. For the console interpreter, we don't need to do anything here; the interpreter takes care of setting up the display window for us.
Generate HTML to wrap the left/right portions of the status line. The basic status line has three stages: stage 0 precedes the left portion, stage 1 comes between the left and right portions, and stage 2 follows the right portion. If we're listing exits, we get two more stages: stage 3 precedes the exit listing, stage 4 follows it.
Shut down the user interface. The library calls this once just before the game is about to terminate.
TADS 3 Library Manual
Generated on 5/16/2013 from TADS version 3.1.3