Copyright © by Gerhard Leibrock
1 Requirements | What do I need to get it running? | |
3 Distribution | What’s in this package? | |
2 What is MakeInfo? | Some notes about makeinfo. | |
4 Why WB-MakeInfo? | Why one should use a WB-Interface. | |
5 How to use it | How to use the WB-Interface. | |
Index | Sorted Index. |
[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Makeinfo runs only with version 2.04 or any higher version of the operating system.
In order to run the WB-MakeInfo package you also need
[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
MakeInfo 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.
[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This package only contains my stuff for the WB usage of MakeInfo. To obtain MakeInfo, AmigaGuide, TeX, or BMake check out at your local BBS, the AmiNet sites, Fish disks or somewhere else.
[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
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 MakeInfo package to be installed. It will cost you about 7.5 KB, but you get a full development environment with a primitive sample text.
[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
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 you have to do this manually. It is not difficult at all, just read the “CBM-Install” file carefully.
You will be asked for the path to install WB-MakeInfo and after that it will be installed there (Costs about 30 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.
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.
Do not translate the .texi file via WB-MakeInfo and CEd while you watch it with a hypertext viewer. This will cause an error message (Object in use …)
5.1 Setting up a .texinfo environment | ||
5.2 Working with CEd and ARexx | ||
5.3 Producing .dvi or .doc files |
[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Double click on the “WBMG-SetUp” icon. You will see a GUI to specify the path where the .texinfo environment should be installed in.
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.
If you entered the name “MyDoc” then the .dvi, .doc files will also be named “MyDoc”.
5.1.1 The created icons and files |
[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Now you have installed WBMakeInfo 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:
Click it double to activate the execution of the makefile “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.
This file contains the error messages created. Double click on it to see them.
filename
.texiThe “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
.guideThis 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).
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 !
[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
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
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.
[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
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.
[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Jump to: | D H P R S T W |
---|
Jump to: | D H P R S T W |
---|
[Top] | [Contents] | [Index] | [ ? ] |
[Top] | [Contents] | [Index] | [ ? ] |
This document was generated on July 22, 2024 using texi2html 5.0.
The buttons in the navigation panels have the following meaning:
Button | Name | Go to | From 1.2.3 go to |
---|---|---|---|
[ << ] | FastBack | Beginning of this chapter or previous chapter | 1 |
[ < ] | Back | Previous section in reading order | 1.2.2 |
[ Up ] | Up | Up section | 1.2 |
[ > ] | Forward | Next section in reading order | 1.2.4 |
[ >> ] | FastForward | Next chapter | 2 |
[Top] | Top | Cover (top) of document | |
[Contents] | Contents | Table of contents | |
[Index] | Index | Index | |
[ ? ] | About | About (help) |
where the Example assumes that the current position is at Subsubsection One-Two-Three of a document of the following structure:
This document was generated on July 22, 2024 using texi2html 5.0.