Click above to get retro games delivered to your door ever month!

   [  Making source files  ]

   The data in a Norton Guide database file is presented to the user as

      a menu
   or
      a list of short entries
   or
      a long entry

            +----------------------------------------------------+
            | At any one time, the database program can display  |
            | either a list of short entries, or one long entry. |
            +----------------------------------------------------+


   Each menu item expands into either a list or a long entry (selected in
   the menus by the user).


   Each item in a list of short entries can expand into
      a) a long entry                 which is the typical use
      b) a list of short entries      i.e. another list
   or
      c) nothing                      blank lines make the list easier
                                      to read
   A list typically works as an index to the underlying long entries.


   A long entry (you're currently reading one) does not expand into
   anything. It can, however, contain one or more cross-references
   (see-also's, see the ones above) to other long entries.



   Following this structure, you create one link file, and a number of
   source files (one for each menu item defined in the link file).
   Each source file must contain either
      one long entry
   or
      a number of short entries, each followed by
           a) a long entry
        or b) a reference to another list

   You can name these files anything you want (file extensions .NGO and
   .NG excepted). But, to make the compilation and linking easier, it's
   practical to give all source files the same file extension (e.g. .TXT
   for text, .ASC for ASCII, or .NGS for Norton Guide source), and the
   link file another (e.g. .LCF for link control file).