This program being a frontend (or backside?) to the psutils package written
by Angus Duggan. The version here is 1.3 Patchlevel 13 which I believe to be
the latest, unless anyone cares to prove otherwise.
Copyright and all that ...
--------------------------
Anything in the bin and man directories are covered by the LICENSE file in the
!PSUtils application directory. `bin` contains the psutils programs as compiled by myself. The source code needed only one small change and everything I've
tried seems to work. `man` contains a text version of the manual pages for the psutils package, with in that directory is another called `man1` which contains the original source for the manuals.
Everything else was done by me and is all my fault. Basically I've written a Wimp based front end to the main programs to save you having to use nasty horrible command line options. The frontend is written in Basic, using BLibII by Ian Palmer (and libraries by Tom Hughes).
Use
---
The icon bar menu has the usual Info and Quit options. In between them are the 6 psutils programs. There is a tick beside the currenty selected one. Change this by clicking on the appropriate menu entry. Every one of the programs has a submenu which allows the configuration window for that program to be opened.
Clicking select on the iconbar icon will open the confiuration window for the currenty selected program.
That's about it except to say that once you've setup the options drag a postscript file to the icon on the iconbar and a savebox will popup. Drag the Icon to a filer window as normal and the Postscript will be processed by the currently selected program. (Default is psnup).
What are all the options?
-------------------------
Hopefully they're at least slightly self explanatory, they certainly should be if you've used the programs before. If not then take a quick look at the manual pages, everything is described fully there.
For all but the pstops program I've merely given all the command line options a button, writable thing or whatever to allow the option to be adjusted.
The options are only updated when you click the OK button.
For pstops I've gone a bit further. A pagespec must be given to tell pstops what to do with your pages. I've decoded this and given a graphical representation in the window. Double click on the window and you get a larger view. Pages with the same outline colour will be on the same real sheet of paper (unless you have more than 8 pages in a group, then the wimp colours wrap around again!). That means that pages with a different colour will definitely be on different sheets.
Read the manual for a description of the syntax of the page definition, or fiddle with the definition there and see what happens. Dimensions can be supplied as 'in', 'mm', 'cm', or 'pt' (points = 1/72 inch). No units implies points.
Eventually it should be possible to drag the page outlines in the overview window to alter the page definition toy your liking.
Anything else ...
-----------------
If anyone wants the source to the psutils programs then just ask.
The Frontend program (!RunImage and all the associated files) remain copyright Graham Jones, 1995. Please distribute all over the place, just don't charge anyone for any of this stuff.
If anyone actually finds this stuff useful, has any suggestions, finds any bugs (see below) etc etc please let me know.
There are several perl scripts that I haven't included in the archive since I haven't tested them. They are largely to do with correcting the Postscript output by various applications so that the file is usable with the psutils programs. I may deal with these in time, alternatively they may never be touched! The manuals are supplied, if you want any of the scripts get intouch and I'll pass them on.
As far as I am aware the Acorn Printer drivers produce Postscript which the psutils programs can handle.
Bugs
----
In the event of finding a Bug roll up a newspaper and apply a hard downward swiping action.
Alternatively, if it's a problem with the frontend then tell me what you were doing, what options were set and I'll see if I can repeat it and possibly fix the problem.
If you have a problem with the Postscript produced I'm willing to investigate.If the same behaviour occurs with the UNIX versions of the programs then it would be best to take it up with Angus Duggan. (Which might be tricky, there seems to be no contact details in the original archive!)
If there is a problem with the Acorn version only then I'll look into it.
