Welcome to the great world of GNU TeXInfo and the Amiga port done by Reinhard Spisser and Sebastiano Vigna. Reinhard Spisser Via Licurgo 12 I-20162 Milano MI BIX: reinhards@bix.com INTERNET: spisser@ghost.sm.dsi.unimi.it rein@bliss.st.dsi.unimi.it Sebastiano Vigna Via California 22 I-20144 Milano MI BIX: svigna@bix.com INTERNET: vigna@ghost.dsi.unimi.it UUCP: seba@sebamiga.adsp.sub.org This document describes the usage of the Workbench interface done by Gerhard Leibrock. Gerhard Leibrock Neuhäuselerstr. 12 66459 Kirkel 2 Germany INTERNET: leibrock@fsinfo.cs.uni-sb.de `The guide to WB-MakeGuide' *************************** (C) by Gerhard Leibrock, 1993 Done using GadToolsBox V2.0b (C) by Jaba Development and DICE/C (C) by Mathew Dillon Requirements ************ Makeinfo runs only with version 2.04 or any higher version of the operating system. In order to run the WB-MakeGuide package you also need * Cygnus Ed Professional, a COMMERCIAL (NOT PD or SHAREWARE) product done by ASDG. * AREXX, gets delivered with every OS 2.x or higher. * The AmigaGuide package from Commodore (public domain) or any compatible viewer to use the hypertext output. * A TeX implementation for the Amiga (I recommend PasTeX, a PD package) to use/print out the .dvi output. * An ASCII text viewer to use the .doc output (e. g. More from workbench) * the public domain make utility BMake done by Ben Eng or something compatible to it (If you use a different program DO NOT forget to edit the file "Do_It" in the directory "Package" and change the line containing "Bmake" and replace this with your favourite make utility. What is MakeGuide? ****************** MakeGuide was developped by the GNU people in order to provide an easy way to make technical documentation. Nowadays there exist three major kinds of documentation: `Hypertext documentation' It is easy to use and certainly the best kind of electronic documentation. `ASCII documentation' It can be used with primitive viewers, which are available on most platforms. It can be printed out on almost any printer without difficulties. `documentation in .dvi format' Extrem useful for people who don't like electronic documentation and prefer the printed ones. The .dvi documentation can be shown with a special program and printed out. The printout looks very professional, lots of technical books were written using TeX. It requires TeX installation on the specific system and a good printer. These three kinds of documentation can easily be generated by just ONE (1) source file in a specific format, called Texinfo. It is easy to learn and the required programs to generate the output are public domain. It is very useful for programmers to save time, because you just have to look at only one file and not at three and you don't have to learn TeX or the hypertext format, only TeXinfo. Distribution ************ This package only contains my stuff for the WB usage of MakeGuide. To obtain MakeGuide, AmigaGuide, TeX, or BMake check out at your local BBS, the AmiNet sites, Fish disks or somewhere else. Why WB-MakeGuide? ***************** If you often use Texinfo, to generate your documentation and you like the workbench, then this will be a great help for you. All you have to do is to click on the SetUp icon and enter a path for the MakeGuide package to be installed. It will cost you about 7.5 KB, but you get a full development environment with a primitive sample text. How to use it ************* Un-Lha the package to anywhere you like to, e. g. the RAM-DISK. If you do have the CBM installer accessible in your system, then click on the "CBM-Install" icon, else click on the "PoorPeople-Install" icon. You will be asked for the path to install WB-MakeGuide and after that it will be installed there (Costs about 40 KB). To use the delivered scripts with CEd I recommend to assign them to a function key. If you have done so then you can translate your .texinfo file into a .guide file by just pressing an f-key. Remember: The CEd development environment is ONLY able to produce .guide files. If you want to produce .dvi or .doc files then you have to activate the "Do_It" icon. Warning: Do not translate the .texi file via WB-MakeGuide and CEd while you watch it with a hypertext viewer. This will cause an error message (Object in use ...) Setting up a .texinfo environment ================================= Double click on the "WBMG-SetUp" icon. You will see a GUI to specify the path where the .texinfo environment should be installed in. 1. Path You can either enter the path by hand or click on the gadget containing the "F" to use the ASL-filerequester. Remember: The installed .texinfo environment will always be in a directory "Package". E. g. if you specified "Work:Texts" then the setup program will generate a directory "Package" and copy the needed files into it. 2. Name of .texi file The name of the source code file. This name will also be used automatically for the .doc and .dvi file. E. g.: If you entered the name "MyDoc" then the .dvi, .doc files will also be named "MyDoc". 3. Name of .guide file The name of the hypertext output can be choosen seperately. 4. Install Install the package 5. Forget it Quit program The created icons and files --------------------------- Now you have installed WBMakeguide and you see a new directory named "Package". You can re-name it and give it a name you like more. If you enter it, you will see 8 created icons: Do_It Click it double to activate the execution of the makefile "Make4Guide". Make4Guide The makefile for your texinfo document. Double click on it to get it loaded into CEd. The only line of importance for you is the 6th line: Here you can specify what output to create, a .dvi file, a .doc file (ASCII) or a .guide file (AmigaGuide format). Simply erase guide, doc or dvi if you don't want it to be created. AllGuide.err This file contains the error messages created. Double click on it to see them. `filename'.texi The "source-code" for your documents. Double click on it to get it loaded into CEd. A simple file was created automatically to make editing easier. `filename'.guide This file will contain the .guide output. Double click on it when created and it will be loaded into AmigaGuide (SYS:UTILITIES/AMIGAGUIDE) `filename'.doc This file will contain the .doc output. Double click on it when created and it will be loaded into the ASCII viewer More from workbench (SYS:UTILITIES/More). This file will contain a plain ASCII version of your text. `filename'.dvi This file will contain the .dvi output created by virtex. Double click on it when created and it will be loaded into ShowDVI, a previewer for .dvi files delivered with the public domain software package PasTeX (Available on Fred Fish CDs or from any good PD seller/distributor). Del-TeX-Trash This icon will delete files that were created by virtex (creation of .dvi file) and that are no longer needed. Be warned ! It delets without warning ! Working with CEd and ARexx ========================== Just click on the .texi file and the source will be loaded into CEd. Here you can edit it and "compile" it using the ARexx scripts (The best way is to assign them to a function key.). The ARexx scripts are 1. Start_MGuide.ced Used to start the MakeGuide program from CEd. Should be invoked to start translation. 2. MGuideErr.ced Used by "Start_MGuide.ced" to help the user to debug the source. It can also be invoked seperately by the user. E. g.: I did assign the "Start_MGuide.ced" command to F3, so I start compiling by pressing F3. The "MGuideErr.ced" command was assigned to F4, so I can debug the file by pressing F4. Producing .dvi or .doc files ============================ It is not possible to generate .dvi or .doc files via the "Start_MGuide.ced" command because this is unnecessary and ment too much work for me. The best way is to work with the environment and produce .guide files for syntax checks. If everything works ok, then use "Do_It". The only way to produce a .dvi or .doc file is to start "Do_It" from workbench. By default it generates a .guide, .doc and .dvi file. If you don't like this default setting simply edit "Make4Guide" by double clicking it and change the line "all: guide doc dvi" to something like "all: doc dvi" for just generating .doc and .dvi files. Index ***** Distribution Distribution How to use it How to use it Producing .dvi or .doc files Producing .dvi or .doc files Requirements Requirements Setting up a .texinfo environment Setting up a .texinfo environment The created icons and files The created icons and files What is MakeGuide? What is MakeGuide? Why WB-MakeGuide? Why WB-MakeGuide? Working with CEd and ARexx Working with CEd and ARexx