Difference between revisions of "CellarDoor"

From IFWiki

Line 1: Line 1:
[[CellarDoor]] is a new [[Z-machine]]/[[Glulx]] [[interpreter]] for PalmOS (RC1).
[[CellarDoor]] is a new [[Z-machine]]/[[Glulx]] [[interpreter]] for PalmOS (RC2).
Its creator and maintainer is [[Jeremy Bernstein]].
Its creator and maintainer is [[Jeremy Bernstein]].

Revision as of 22:14, 9 April 2007

CellarDoor is a new Z-machine/Glulx interpreter for PalmOS (RC2). Its creator and maintainer is Jeremy Bernstein.

CellarDoor is an Inform (Z-Code and Glulx) interpreter for PalmOS. It is based on the code of Fangorn’s CliFrotz 1.6. As such, CellarDoor maintains support for Z-Machine story files, while adding support for Glulx stories, as well as Z-Machine and Glulx stories wrapped in the Blorb file format (.zblorb and .gblorb files).

CliFrotz was based on the Frotz v2.43 interpreter. Frotz is an Interactive Fiction interpreter that plays Z-Machine (Infocom, Inform, Z-Code) games such as Zork and Hitchhiker’s Guide to the Galaxy. CliFrotz supported V1-V8 games and V6 MG1 graphics.

CellarDoor adds Glulx support via the Git interpreter (1.1.3) and uses a modified version of the CheapGlk library (0.9.0). It supports JPEG and PNG graphics, if they are found in Blorb files.

It requires a hi-res screen, OS4 or later, an expansion card and the large dynamic memory area available from OS4 onwards.

If your handheld does not meet these requirements, you may want to try Frobnitz, PilotFrotz or Kronos.

Principal changes in CellarDoor (relative to CliFrotz):

  • Support for Glulx (.ulx), .zblorb and .gblorb files, including Autosave.
  • Previous support for Z-Code has been updated to accomodate games produced with Inform 7 (with greater memory demands)
  • Support for scalable Blorb graphics (JPEG and PNG)
  • Categories


  • Notes
  • 2nd Word List (for multilingual users)
  • Quetzal save files now written to per-game folders to help avoid naming collisions.
  • More predictable Landscape mode support


  • Now compiling with gcc (prc-tools) instead of CodeWarrior
  • Using PEAL for ARMlet support
  • Using multilink for lazy code sectioning
  • Many, many, many bug fixes/memory leak plugs.