> Just picking up on a small point.
>
> > I don't know whether Steve has worked out the implications of all this for
> > his debian/ubutu -based version of poplog.
>
> I think this question was scoped to popvision. The build process does
> recompile all the C-files as shared objects. It does not create the popvision
> saved image but I will take a look at that tonight. I think that's all that
> is needed for popvision.
I guess most people will not want it pre-built, as it is so easy to create if
needed.
However, for testing your system, you could also have a bit of fun if you try
creating the gblocks saved image
$usepop/pop/packages/rclib/mkgblocks
The printout during building is a bit messy and could be modified as it is
irrlevant to the context of building a saved image (my fault):
;;; LOADING LIB rclib
;;; LOADING LIB rc_blocks
TO START THE PROGRAM TYPE:-
blocks_go();
or
ENTER blocks
;;; LOADING LIB xved_standalone_setup
mkgblocks done
If it gets that far, type:
pop11 +gblocks
type 'y' when it asks if you want xved.
Type 'help' in the xved window -- which should come up alongside the 2D image of
tabletop scene.
It gives some example commands. Move the ved cursor to one, edit if desired,
and press RETURN, e.g. you can select one with a multi-parse example:
put the block on a block on a block on a red block
You can also change some words before RETURN.
after printing each parse or displaying it graphically, it asks you to click on
'continue', and also after each step in plan execution.
Inspired by Winograd's thesis, 1971. But much simplified.
Running on Sun workstations (or Xterminals), this used to entertain visitors on
opendays in the 1980s, long before all the fancy stuff became available on the
internet!
A 'big' server might have a few hundred MB of memory in those days -- much less
than my mobile phone now.
Aaron
