[To reply replace "Aaron.Sloman.XX" with "A.Sloman"]
cglur@onwe.co.za writes:
> Date: 23 Mar 2002 12:20:36 GMT
> Organization: The South African Internet Exchange
> ...
(after restoring missing system files.)
> Well (mc and) poplog seems to run OK now.
> Except I couldn't even remember how to zoom and swap 'windows',
> after being off poplog for 8 months. Luckily I always collect
> (cutNpaste) notes. The teachved is good for beginners, but I'd have
> a nervous breakdown if I had the go through it again to get up to speed.
Correct.
It may be useful to remember that besides the TEACH files which are
intended to be slow-moving enough for beginners, there are HELP
files which often give a lot of useful summaries, and REF files
which give more technical information.
The boundaries between the categories are not sharp, however.
For example this file summaries key-strokes available in Ved/Xved
HELP vedkeys
but NOT including function keys, which vary between terminals. (Emacs
users will probably like this one.)
The function key bindings we use here are described in:
http://www.cs.bham.ac.uk/research/poplog/help/vedncdxtermkeys
(used here for Xterminals, PCs, Dec Alphas, Suns, etc.)
This one gives an overview, pointing to a large number of information
files:
HELP ved
The following REF files describe the main ENTER commands available and
the main lower level functions that can be invoked by either ENTER
commands, key-strokes, or use programs:
REF vedcomms
The main Enter commands (others may be defined in
local libraries, particular applications that use Ved as an
interface, etc.)
REF vedprocs
Ved programmer interface (some of it!)
Note, a procedure to simulate an ENTER command can use
veddo('<enter command>');
REF vedvars
The main sets of program-accessible variables that control
ved.
I have a fairly short set of notes which summarises most of the
frequently used items from the above, prepared for users in birmingham
and included with the bham extras:
http://www.cs.bham.ac.uk/research/poplog/teach/vednotes
It may be that the function keys as described there work differently
from your function key setup, but you could copy the file and edit
it to provide a local summary.
It does not yet include the most useful Xved commands, e.g. commands for
changing font or changing window size, or foreground and background
colours in Xved.
See TEACH xved
HELP xved
REF xved
(these are non-redundant)
If you are running X you can use my rcmenu package for controlling Ved
via menus without having to run xved.
It provides what I call a "recursive hypermenu system" which is
easily user extendable.
You'll need to untar these two files into $poplocal/local
http://www.cs.bham.ac.uk/research/poplog/rclib.tar.gz
http://www.cs.bham.ac.uk/research/poplog/rcmenu.tar.gz
After it is installed and the main functions are compiled,
ENTER menu
or
ENTER menu toplevel
invokes a menu panel from which other menu panels can be invoked
automatically if they are defined by files in this directory:
$poplocal/local/rcmenu/menus/menu_*.p
where the * is replaced by the menu name.
E.g.
ENTER menu compiling
loads the file
$poplocal/local/rcmenu/menus/menu_compiling.p
which can also be loaded by clicking on the 'Compiling' button on the
toplevel menu. Menus can invoke one another. To see what menu
definitions look like peek at these:
http://www.cs.bham.ac.uk/research/poplog/rcmenu/menus/menu_toplevel.p
http://www.cs.bham.ac.uk/research/poplog/rcmenu/menus/menu_compiling.p
http://www.cs.bham.ac.uk/research/poplog/rcmenu/menus/menu_mark.p
The menus are trivial to alter if you want them to include different
options, different font sizes, different colours, one column or two
columns for the menu buttons, etc. E.g. here are some button definitions
in the mark menu:
['HELP mark' 'menu_doc help mark']
['TEACH mark' 'menu_doc teach mark']
['MarkStart' vedmarklo]
['GoStart' vedmarkfind]
['MarkEnd' vedmarkhi]
['GoEnd' vedendrange]
['DelRange' ved_d]
['YankBack' ved_y]
['CopyRange' ved_t]
['MoveRange' ved_m]
['MoveIn' ved_mi]
['CopyIn' ved_ti]
['MoveOut' ved_mo]
['CopyOut' ved_to]
['MarkAll' ved_mbe]
['Move...' [MENU move]]
['Editor...' [MENU editor]]
etc.
The string on the left of each list is shown as a menu button. The rest
of the list specifies what to do when the button is selected. Some
buttons can invoke a panel asking for arguments, not shown here.
The last two buttons shown invoke other menus.
The menus are invoked by one click which brings up the menu, usually at
bottom right of the screen.
By default the panels stay up unless you click on 'Dismiss'. So you
don't have to give yourself RSI by continually dragging a mouse pointer
around.
Frequent users usually eventually learn all the commands they use most
often so that they don't need these menu panels any more. For a novice
or infrequent user they can be very useful. Some of our students go on
using them throughout their three years here. Others get rid of them
after a short time because they learn the more direct commands (my
intention).
Aaron
====
Aaron Sloman, ( http://www.cs.bham.ac.uk/~axs/ )
School of Computer Science, The University of Birmingham, B15 2TT, UK
EMAIL A.Sloman AT cs.bham.ac.uk (ReadATas@please !)
PAPERS: http://www.cs.bham.ac.uk/research/cogaff/ (And free book on Philosophy of AI)
FREE TOOLS: http://www.cs.bham.ac.uk/research/poplog/freepoplog.html
|