Update printer dev documentation with text info

doc/web/src/site/apt/developing.apt

@@ -145,23 +145,21 @@ easy.  Start with <<<vars_x86linux>>> if you are a little-endian machine, or
 unless your processor is little-endian (x86, Alpha).  Mac, Sun, MIPS,
 HP, Motorola, and IBM are big-endian.
 
-* Incorporating Parallel Printer Support 
+* Incorporating Graphical Printer Support 
 
- Until parallel printer support is generally integrated into all builds, the following work needs to be done:
+ Until graphical prallel printer support is generally integrated into all builds, the following work needs to be done:
 
  * Install Simple DirectMedia Layer ({{{http://www.libsdl.org/}SDL}}) and Freetype in your build environment - you'll need to link to their libraries 
 
- * Add <<<-DHAVE_PARALLEL>>> to the <<<CCOPTS>>> variable in your <<<vars>>> file; also add  <<<-DWIN32>>> if you're on Windows
+ * Add the <<<-DHAVE_SDL>>> option to your <<<CCOPTS>>> and add the same (perhaps to a new) <<<CPPOPTS>>> in your <<<vars>>> file
 
- * Add something like <<<-I/usr/include/freetype2>>> and <<<-I/usr/include/SDL>>> options to your <<<CCOPTS>>> in your vars file to point to the SDL and Freetype include files   
+ * Add something like <<<-I/usr/include/freetype2>>> and <<<-I/usr/include/SDL>>> options to your <<<CCOPTS>>> and add the same (perhaps for a new) <<<CPPOPTS>>> in your <<<vars>>> file to point to the SDL and Freetype include files
 
- * Compile <<<parallel.c>>> and <<<printer.cpp>>> and include their object code as part of your final linkage
+ * Include SDL and Freetype libraries to <<<EXTRA_LIBS>>> in your <<<vars>>> file (i.e. <<<EXTRA_LIBS = -lSDL -lfreetype>>>)
 
- * Include SDL and Freetype libraries as part of your final linkage (i.e. <<<-lSDL -lfreetype>>>)
+ * Include the Win32 common dialog library to <<<EXTRA_LIBS>>> as part of your final linkage if you're on Windows (i.e. <<<EXTRA_LIBS = -lSDL -lfreetype -lcomdlg32>>>)
 
- * Include the Win32 common dialog library as part of your final linkage if you're on Windows (i.e. <<<-lcomdlg32>>>)
-
- * After building, you'll need the file <<<parallel.rom>>> in the same directory as your GSport executable
+ * After building, you'll need the file <<<parallel.rom>>> in the same directory that <<<config.txt>>> is found
 
  * You'll probably want a monospaced TrueType font file easily accessible to add as part of the GSport configuration
 

doc/web/src/site/apt/printer.apt

@@ -29,14 +29,34 @@ GSport Emulated Printer
 [images/printer2.png]
 
  Printer Timeout configures how long until a form feed is automatically sent to the printer 
- (which forces the emulator to kick out a "page".)
-It should be set higher for PR#1-type printing to work correctly. 
+ (which forces the emulator to kick out a "page").
+It should be set higher for PR#1-type printing to work as you might expect. 
 If it is set to "Never", you have to manually send a form feed, fill a page with text, or exit the emulator before any output is saved.
 This behavior is similar to modern laser/inkjet printers when they are used with Applesoft. 
 Most applications are good about sending form feeds at page end, so this issue usually doesn't crop up.
 
  Make sure to configure font locations.
- Roman is used by default and the printing emulation won't work if none at all are defined. 
- Any monospaced truetype font you have will work.
+Roman is used by default and the printing emulation won't work if none at all are defined. 
+Any monospaced truetype font you have will work.
 
  Printer output should appear in the same directory as GSport as page1.bmp, page2.bmp, etc.
+
+* Printer Output Type
+
+ GSport can produce various types of graphical or textual output based on your platform and 
+ what has been compiled into your binary.
+ Cycling through the various options in "Printer Output Type," there are:
+
+ * Windows Bitmap
+
+ * Postscript (B&W)
+
+ * Direct to host printer
+
+ * Text file
+
+ []
+
+ Windows Bitmap will produce .BMP files for each "page" produced.  The same is true for Postscript, but .PS files are produced.
+"Direct to host printer" is only implemented for Windows, and will send page-oriented output directly to your system's printer.
+"Text file" will append text-only output to a file named "printer.txt" in GSport's current working directory.