home *** CD-ROM | disk | FTP | other *** search
- .setu 10 :arc:
- .// Source for !jgp.Info.!clickme; revised Tue,20 Apr, 1993
- .//
- .// This text is designed for Arc Desktop users; MSDos and Commandline users
- .// may find some information irrelevant and other needed information
- .// requiring imaginative interpretation.
- .//
- .// Some control directives help with character positioning in the line when
- .// this is printed in proportional spacing; ignore them. (.\ \Q, .usel), .setst
- .// and .nost organise undenting.
- .sp 0 Comment this line out (.//) for paged output (66 lpp)
- .hd
- /.col
- |JGP Introduction v1.20|Fri,03 Jul 1992
-
- /
- .ft
- /
-
- .col
- |-\p-
- /
- .ht 18
- .marg 2 79
-
- .\ \Q
- .col
- |JGPrograms
- .col
- |==========
- .usel base
-
- The application !jgp makes available the Jolly Good Programs Tools. These are:
-
- .setst :\t:
-
- .nost
- JGEd: \t}a very powerful editor;
- .nost
- JGPrint: \t}a text formatting and printing program;
- .nost
- JGConfig: \t}Builds or modifies Printer Configuration files;
- .nost
- JGPCopy: \t}Desktop Handler to copy to screen, Dump or print JGPCopy files;
- .nost
- JGPrSlave \t}Prints for JGPCopy via !Printers if required.
- .nost
- !runimage: \t}Desktop Handler for JGPrint-JGConfig desktop icon and options;
- .nost
- JG<misc>: \t}various miscellaneous JGUtilities to go in the library.
- .setst ::
-
- NB icons on the icon bar will change, perhaps unexpectedly; see 'Icon
- transmutation' below.
-
- The usual !boot, !run, !runimage, !Sprites and Templates live in !jgp.
- JGEd-JGPrSlave live in the Tools subdirectory of !jgp; various auxiliary files
- (see below) must also live in the Info subdirectory of the !jgp directory for
- the application to work, and, in particular, to provide online documentation in
- JGEd and JGConfig; the pa and q subdirectories contain configuration and font
- files.
-
- Except for JGEd and JGPrint, for which licence fees are payable, all programs
- are distributed without charge subject to the conditions specified in JGLiceDoc,
- JGCopydoc and derivatives thereof. The shareware disk holds JGSharED and
- JGSharePr: substitutes with restrictions (see below) for JGEd and JGPrint,
- which, unlike those on some demo disks I have seen, are by no means totally
- useless. All programs are copyright (C) JGLaski, 1992.
-
- JGPrint/JGSharepr can be put into JGDoc(ument) mode, and in this mode JGSharePr
- loses its shareware restrictions; I distribute the system in this mode. See
- discussion below.
-
- The directory Docs contains JGPrint files that document JGEd, JGPrint, JGPCopy,
- JGConfig, JG<misc> and detail licensing rules. Start with JGDocdoc for the doc
- mode of JGPrint (JGDoc). These files are themselves JGPrint files, and,
- although, as ascii files, they can be read in any editor (e.g. drag them to the
- JGEd icon), to obtain well\-laid out texts, apply JGDoc/Print to them by double
- clicking on their own icons. For JGDoc, these will be JGPcopy files in a
- directory docs.doc, and double clicking on these will, via a menu, show them on
- screen or send them to your printer.
-
- [The 'Learner Driver's Manual' in the directory Driman is designed to provide a
- beginner's guide to JGEd/JGPrint for people without much computing or
- word\-processing experience.]
-
- What follows details the operation of the JGP suite, explains how the files
- should be installed and documents desktop operation that may not be obvious from
- the menus; I recommend you skim it, at least, on first reading.
-
- In principle, throughout these programmes, when textual prompts occur, the keys
- for the various responses are shown in brackets. Any other key denies the
- suggested responses; on the mouse, Select is usually equivalent to the first
- suggested response and Adjust to the second (often a denial). In principle, the
- usual way through each dialogue is obtained by a sequence of Select clicks.
-
- In the desktop, JGEd/Print/Config all engage the user in a dialogue. Therefore,
- they use the whole screen, but while waiting for user input, enable the
- processor to get on with any concurrently active desktop task. Moreover, they
- can be 'hidden' in a latent desktop window in order to have full access to the
- desktop; thence, clicking on their window brings up a menu to continue their
- user dialogue, or other appropriate actions.
-
- As soon as the !jgp application is opened in a filer viewer on the desktop, it
- sets the system variable jgp$dir to <path>.!jgp and defines and provides icons
- for four types of files, JGPrint, JGEd, JGPConfg and JGPCopy. It also sets
- Tools.JGPcopy to print any files of type JGPCopy for the printer manager. If the
- JGPCopy standalone application is active, this latter will be caused to quit
- without, of course, losing any files that are being printed or viewed. (NB. as
- at 1/93 a potential bug, and how to get round it, is reported.)
-
- .col
- |The Icon bar Icons & their Transmutation
-
- Double clicking on !jgp will register a JGEd icon on the icon bar. Double
- clicking on any file of type JGEd, JGPrint or JGPCopy will apply, respectively,
- JGEd, JGPrint or JGPCopy to that file; if an icon bar icon has not yet been
- registered, a JGEd icon will also be registered on the icon bar, irrespective of
- which type of file was double clicked.
-
- In the normal case, dragging a file to the icon bar icon will apply
- JGEd, JGPrint or JGPCopy to it, according to which icon is on the icon bar.
-
- However, the choice Settype in the icon bar icon menu, if ticked, will, once
- only, unless " + hold" below it is also ticked, set a file's type to whichever
- of JGEd, JGPrint, JGPCopy has its icon on the icon bar when the file is dragged
- to the icon bar icon.
-
- In the icon bar menu, and its options submenu, those choices that do not
- relate to the icon on the icon bar are shaded.
-
- Clicking select on the icon bar icon transmutes it to a JGEd icon, unless, of
- course, it already is, in which case it transmutes to a JGPrint icon. Choosing
- Jgpcopy in the icon bar icon's menu transmutes the icon to a JGPCopy icon,
- unless, of course it already is, in which case it transmutes to a JGEd icon.
- These rules give priority to JGEd, then JGPrint, then JGPCopy, which reflects
- what the user will find most convenient. Clicking with adjust acts equivalently,
- but also opens the menu.
-
- Dragging a file to the JGPCopy icon, in addition to applying JGPCopy to the
- file, transmutes the icon bar icon to JGEd; this transmutation can be cancelled
- if " + hold" below JGPCopy is ticked.
-
- ,col
- |Options
-
- If the JGEd icon is on the icon bar, you can, from the main menu, arrange
- to create a new file for editing. From the option menu you can, roughly, set the
- size of the buffer within which JGEd will edit. You can also set JGEd to use
- whatever screen mode you require, (NB it uses VDU4 characters), to operate in
- view rather than edit mode, to accept rather than query vdu characters, and not
- to engage its backup facilities.
-
- If the JGPrint icon is on the icon bar, you can, from the main menu, run
- JGConfig, a program to edit configuration files. From the option menu, you can
- set which configuration JGPrint and JGonfig will first offer you. In either
- program,, you may, of course, reject this first choice, and you will be shown
- the choices available. Configuration files and proportionally spacing files are
- held in the directories ...!jgp.pa and ...!jgp.q; the file !jgp.AJGCdnames is
- used by JGConfig.
-
- If the JGPCopy icon is on the icon bar, you can, from the main menu, arrange to
- hold it on the icon bar as described above.
-
- Please explore the various option menus to see what flexibility is provided.
-
- .col
- |Screen Modes
-
- All the JG programs will work in all screen modes. Howver, 16 colour modes are
- recommended, particularly for JGEd. JGEd starts in the desktop mode unless
- another mode were chosen from the option submenu of the JGEd iconbar icon menu;
- this menu, as the JGPCopy run menu accesses a window whose icon enables you to
- cycle through the available 16 colour modes.
-
- JGEd allows a more detailed control via its extended command md<n>.\|
-
- JGPrint's initial dialogue takes place in its own window; so can its operation.
- However, depending on what you choose to JGPrint To, you most probably will be
- offered the choice of running in the desktop; if so, via JGPrint's menu, you may
- swap between the two ways of running as you wish.
-
- .col
- |From the commandline
-
- JGEd, JGPrint, and JGConfig work equally well from the commandline. You have
- to set jgp$dir to <path>.!jgp by hand. I recommend putting the files (J)ed and
- (J)print in the library, together with JGExist, which they call on. Then
- JGEd/SharEd and JGPrint/JGSharePr are available irrespective of what
- directory you are in. The JGPrograms no longer use the other JG<misc> programs,
- but I have not wiped them in case they can be useful elsewhere. JGEd has a
- switch -b <n> to choose your editing buffer size. If you do not give JGEd a file
- argument, you will see a list of the switches available.
-
- All the JGPrograms will work without extra arguments on the commandline,
- engaging the user in a dialogue to evoke those they need; personally, I usually
- give JGEd the name of the file it is to work on from the commandline, but not
- JGPrint or JGConfig.
-
- If the desktop is not present programs run with bright colours on a dark
- background (which I prefer) rather than dark colours on a white background.
-
- Without the desktop and unnecessary modules present, JGEd can grab a bigger
- buffer, and therefore edit enormous files. I doubt that this will concern
- people with more than 1Mb of store.
-
- NB under Riscos 2 running from the F12 window is fine. but Riscos 3.1 gives a
- "Wimp is currently active" complaint; you can successfully click on j(ed) in the
- library or on Tools.JGEd.
-
- .col
- |JGDoc v. JGPrint Mode
-
- JGDoc mode provides a cut-down use of JGPrint that avoids the need for
- configuration files, simply producing a laid\-out JGPCopy file that can be
- clicked on either to view or to pass to the printer. Printer commands are not
- produced. JGPrint capabilities that depend on auxiliary files can be used
- except for initialising user variables from a file. Applied to a JGPrint file
- <path>.foo, JGDoc yields a well\-laid out JGPCopy file <path>.doc.foo, which can
- be double clicked for JGPCopy to show on screen or pass to printer. In JGDoc
- mode JGSharePr has no restrictions relative to JGPrint.
- .if 1
- !Clickme in !jgp.Info was produced by applying JGDoc to this file.
- .fi
-
- If the desktop is active, JGDoc works entirely in the desktop in RisCOS2
-
- See JGDocDoc/Info for details of how the user can arrange to get the page size
- she wants and to get £ to print out correctly on her printer.
-
- JGDoc also provides a range of powerful tools for documenters to organise and
- structure their material. The JGFooDoc files provide a range of examples; in
- particular, JGDocDoc is organised in a quasi-tutorial fashion. All texts
- prepared for JGPrint mode will be accepted and treated sensibly in JGDoc mode.
- (NB. those directives such as changing inter\-line spacing or italicising that
- depend on issuing printer commands will be ignored.)
-
- The file !jgp.Info.JGPStrings lists the strings with which !JGPrint engages you
- in dialogue. See xmp.EXAlien for how to enable it to speak in alien tongues.
- (This will be replaced by Messages in due course.)
-
- The presence/absence of the character '*' as the first character in JGPStrings
- determines whether JGPrint/JGSharePr runs in JGDoc or JGPrint mode. I distribute
- with the * included for JGDoc mode and request that the shareware disk should be
- so passed on. (When Messages have been implemented, an analogous facility will
- be provided.
-
- In JGDoc mode, the printer configuration files in !jgp.pa and !jgp.q are not
- used, and printer codes are not sent to the JGPrinted file. (You can use JGEd
- to edit in the bytes you need, but I think this could only be worth it to
- initialise the printer to the font and line\-spacing you require; on most
- printers you can get the same effect from the front panel.) JGDoc runs without
- an initial dialogue and you can specify auxiliary files for merging or indexing
- when they are needed in the run. (Included files (qv.) work fine.)
-
- The exact interpretation of Hatty directives (^^<char>) in JGPrint mode depends
- on the configuration file used; in JGDoc mode an ad\-hoc convention is used, so
- that is unlikely that you will get the non\-ascii special characters you want
- unless you prepare the text specifically for JGDoc mode.
-
- JGPrinDoc/JGPrintInf documents the JGPrint facilities that depend on auxiliary
- files or configuration files and printer directives. These, of course, are only
- available in JGPrint mode without the initial star in JGPStrings.
-
- .col
- |JGPCopy
-
- This program manages the copying of files to screen and printer, and, through
- its menus, is virtually self\-documenting. One option determines the mode in
- which the file should be seen on the screen, another how many copies of the file
- should be printed. It is entered either by double clicking on a JGPCopy file or
- by dragging any file to a JGPCopy icon on the bar, obtained from a JGEd icon as
- described above. On engaging, it registers a JGPCopy icon with the filename on
- the icon bar, and opens its menu; it also enables a dump of a file to be seen on
- the screen and spooled to a file.
-
- See JGCopyDoc/!ClickJGPC in !jgpcopy for further information'
-
- JGPCopy may also be run from the application !jgpcopy, and, for this use I do
- not charge a licence fee. However, see JGCopyDoc/!ClkmeJGPC for detailed rules
- of the game.
-
- .col
- |!jgMkakeCh
-
- This application builds character definition files for use in JGEd or elsewhere.
- For documentation see JGCharDoc.
-
- .\ \Q
- .col
- |Shareware restrictions
- .col
- |======================
- .usel base
-
- JGSharEd will, as detailed in JGEdDoc, after a few autosaves, refuse to make
- further edits and refuse to save the edited text (a recently updated version
- will be found in autosave>). A user can work out a way to use it without losing
- any editing, but the discipline is a nuisance.
-
- JG(Share)Pr will, after a very few pages, except in JGDoc mode or when
- JGPrinting to screen, insert a random amount of white space and a message
- between the header and the body of the text on the page.
-
- I hope these nuisances will encourage you to buy licences.
-
- .\ \Q
- .col
- |Documentation
- .col
- |=============
- .usel base
-
- Primary documentation is in the directory Docs and consists of:
- .nofj
- .\ \Q
- JGCfgDoc; JGCodeInfo; JGdocdoc; JGEddoc; JGEddoc1; JGLicedoc;
- JGPCopydoc; JGPDiscuss JGPrintdoc; JGPrPrmdoc; Rdmedoc; JGCharDoc
-
- Additional documentation, also available online, is in !jgp.info is:
- !ClickmeJG; Halp_JGEdL; Halp_JGPrn; Help_JGEdI; Help_JGEdK; Help_JGEdL
- Help_JGEdM; Help_JGPrn; jgcfginfo; JGPStrings
-
- In the directory xmp are some examples of advanced uses of JGPrint:
- EXALIEN; ExChars; EXDIARY; exlayout; EXLBL; EXLBLM;
- EXLONGD; EXMERGE; EXMERGM; EXNOTE; EXTAB; EXTIME;
- EXTIMELAY;
- .usel base
-
- After applying JGPrint/Doc to these files, I call them JGDocInfo etc.
-
- !ClickmeJG in !jgp.info is this file Rdmedoc, JGDocced. You should JGDoc the
- others and rename the JGDocced versions JGEdInfo etc. JGCodeInfo is excerpts
- from JGPrint's code that may interest programmers. JGCfgDoc is the source of the
- online file JGCfginfo in !Jgp.info. JGCopyDoc is the source of !ClickJGPC in
- !jgpcopy.
-
- Exlblm and exmergm are merge files for exlbl and exmerge; extimelay is an
- included file for extime; oxdiary is an illustration of the use of exdiary.
- The reader is warned that the directives in these example files, and their
- effects, take quite some thinking out. I reccommend having both the source text
- and the JGDocced text to compare.
-
- !jgp.Tools contains JGEd, JGSharEd, JGPrint, JGSharePr, JGConfig, JGPCopy and
- JGPrSlave; JGEd and JGPrint are not included in the shareware disk.
-
- !jgp.pa and !jgp.q contain printer configuration files used by JGPrint and
- examinable/updateable by JGConfig, as is info.Ajgcdnames. JGPrint requires
- !jgp.pa.default to be present unless used in JGDoc mode.
-
- For running from the command line your Library should contain JEd, JPrint and
- JGExist; The first two are simple scripts which you may find you want to rename.
-
- .col
- |**************
-
- .\ \Q
- .col
- |Licence
- .col
- |=======
- .usel base
-
- JGSharePr, JGSharEd, JGPCopy and all documentation is Copyright JGLaski 1991
- and may be freely used subject to the rules and obligations specified in
- JGLiceDoc, or those texts derived from it.
-
- Jed, JGArcsel, JGBusel, JGExist, JGFtop, JGLength, JGPrepare, JPrint, JGQuery,
- and JGshort are Copyright JGLaski, 1990, and have been put in the public
- domain Nov 1990.
-
- Subject to the conditions detailed in JGCopyDoc, a free licence is available for
- the application !jgpcopy.
-
- A licence for one machine for JGEd is obtainable for £45, for JGPrint for £45;
- the most uptodate versions will, of course, be provided. A combined licence
- forthe pair is £80. A Handling charge of £5 is normally made; for my address,
- see below. See JGLicedoc, for more details.
-
- This disk (without JGED or JGPrint) should be distributed as widely as
- possible.
-
- The use of JGDoc/print for distributed material is subject to licence. See
- JGLiceDoc for details.
-
- No responsibility is taken for the accuracy of these programs, or for any
- consequences of using them, though, of course, every effort has been made to
- ensure their reliability and usefulness.
-
- You are obligated, when passing on this shareware, not to remove any files or
- text.
-
- .col
- |**************
-
- Please tell me of any problems with, or suggest any improvements to, JGDoc,
- JGPrint, JGEd and JGPCopy, and their documentation. See JGLicedoc for the rules
- of the game.
-
-
- .\ \Q
- .col
- | |J.G.Laski |
- .col
- | |18 Ebury Street|
- .col
- | |London |
- .col
- | |SW1W OLU |
- .col
- | |JGPrinted on \d