🚀 go-pugleaf

In article <1609@water.waterloo.edu>, ljdickey@water.waterloo.edu (Lee Dickey) writes:
> ... resource files use a clever encoding scheme that compresses an
> already small quantity of information.  This strikes me as ludicrous,
> since it seems that every file takes a minimum of 1K anyway.  Why not
> store the desired information in "cleartext", perhaps even with a few
> keywords, and allow the user use an editor to create and/or modify the
> input data file?

But, in many cases, these resource files are created with a resource
editor, and the use has no control over the internal format. Although
I haven't needed to create one, I believe there is a standard way to
lay out a GEM resource file. It contains a tree structure describing
the GEM data the program will used, such as dialogue boxes, menus,
etc.
-- 
     Gerry Wheeler                           Phone: (519)884-2251
Mortice Kern Systems Inc.               UUCP: uunet!watmath!mks!wheels
   35 King St. North                             BIX: join mks
Waterloo, Ontario  N2J 2W9                  CompuServe: 73260,1043