Mainly for Bill Wood, but others may be interested. This ends with
instructions on running the Winograd demo.
----
Bill,
[Sorry this is a bit late: I had other things to catch up with.]
It seems to me that you may have left out the second step in my instructions.
FIRST step, set up $usepop: you've done that.
SECOND step (for a bash user):
source $usepop/pop/com/poplog.sh
That will print out
Poplog Version 16 (64 bit)
It also sets up a collection of environment variables that are used in
poplog search lists. E.g. look in
$usepop/pop/com/popenv.sh
or for tcsh users like me
$usepop/pop/com/popenv
Those scripts could be revised to check whether $usepop/pop/packages
exists, and if so to extend search lists to include some standard packages.
Instead, at present (using a temporary 'fix') the searchlist extensions are
done within pop11 in
$usepop/pop/packages/lib/*.p
e.g. this file
$usepop/pop/packages/lib/rclib.p
makes available the rc_graphic libraries and documentation.
['rc' = 'relative coordinates']
If all your paths and environment variables have been set up correctly then
after starting pop11, the command
help rclib
should take you to an overview of the rclib graphic package.
help helpfiles
will give you documentation (probably incomplete and out of date) on
available help documentation. Likewise
help reffiles
help teachfiles
help docfiles [last updated in 1987!]
(We really need an intelligent millionaire to fund a poplog cleanup
project.)
There's lots more information in documentation libraries (teach, help, ref)
and in program libraries (e.g. auto for autoloaded stuff, and lib for files
that have to be explicitly loaded, e.g. using 'lib' or 'uses').
Poplog is a multifunctional monster designed for use both by total novice
programmers using pop11 teach files and for advanced system developers and
everyone in between.
It really needs a brand new overview document. I suspect that if the
proposed transfer of everything to an integrated github site is ever
achieved (not by me -- too old now!) it will require a massive amount of
revision of documentation, especially for new users (like you now!).
Anyhow, if you have not already done so please try:
source $usepop/pop/com/poplog.sh
Then try:
pop11
help rclib
(it asks if you want to use xved (for multi-window interaction with
documentation) or not
Use XVED? (y/n):-
initially type 'n' for a simpler life. If you type 'y' you may get a blank
xved window as well as the help file. Remove the blank window by typing
ESC q
into it, or simply move it out of the way.
Problem: the placing of poplog xved or graphic windows, if not explicitly
specified, sometimes puts them right almost off the edge or almost off the
bottom of the screen, barely visible. I don't know why. But they are
movable, like all X windows.
If you'd like to try the mini-winograd-shrdlu demo do this:
pop11
uses rc_blocks
It will print out: Use XVED? (y/n):-
(choose either y or n).
Move the graphic window out of the way, and type help in the text window.
You'll get some example commands or questions. You can try one or a
variant. (you can move the ved cursor up to one of the examples given, and
then press ENTER, to save typing).
Then follow instructions. Once the demo starts you need to repeatedly click
on the "CONTINUE" button to get the next step, until a command is complete.
Depending on screen size and layout you may have to move temporary displays
of parse trees to expose the continue button at each step. There are
various minor deficiencies in the package, but it can be an effective
demo.
I hope that's helpful and not too confusing....
Aaron
