PICASSO RELEASE NOTES
September 5, 1990

This document describes the picasso directory tree and provides current 
information about the state of Picasso.  You should install Picasso before
browsing through the directories.

1.  The picasso tree.

	Perform an ls -aF on the picasso home directory.  You should see
the following files:

	.clinit.cl		Common lisp initialization file
	.cshrc			Setting up the path and some useful aliases
	.login			A few environment variables
	README			Directory guide
	bin/			Picasso shell scripts and executables
	doc/			Picasso Documentation
	lib/			Picasso libraries
	release/		Picasso sources, build files, and images

	It is useful to print out any relevant picasso documentation
you do not already have.  Most important, in ~picasso/doc, are the reference
manual (ref-man) and the widget writer's guide (widget-guide).  Both of
these are provided in a postscript form as well as in troff-able sources.
You may need to change the makefile to accomodate your printer and system
software.

	~picasso/bin holds a large number of shell scripts used in the
picasso system.  The README file shows what shell scripts are here.  Presently, 
we have defined five architectures:  sun3, sun5, sequent, mips, and 3100.  
At every point where executable or build files are stored, there are 
subdirectories for each of these architectures.  Do not remove these 
directories, since they don't take up much room and allow for easy expansion.

	Now let's taks a quick look at ~picasso/lib.  In the bitmaps
subdirectory all images (monochrome and color) used in picasso are stored.
The po subdirectory holds all of the picasso tools (applications) and
library objects (predefined panels and dialogs).  More information about
these is available in the reference manual.  Other files and directories
here include picasso-defaults (a system-wide default event mapping for
picasso widgets) and directories with library information for specific
tools.  

	Next, we move into the release subdirectory.  Here is where the
code, build files, and images are stored.  The build directory holds all of the
compiled lisp and C files that are loaded together into a single lisp image.
The dumps directory is where the dumped lisp images for Picasso and for an
"enriched" lisp will be stored.  Each picasso user should include the dumps
directory in his path as ~picasso/release/dumps/`~picasso/bin/machtype`
This assures that the correct dump is used for any architecture.  

	~picasso/release/src holds all of the Picasso source code.  First
let's go into the sys subdirectory.  This is where all of the packages that
must be loaded into a vanilla lisp are stored.  Included here are CLX, PCL,
PDS (a source management system for picasso), LIBPQ (an interface to
postgres), CLING (a lisp interface to Ingres QUEL), and SLING (a lisp
interface to Ingres SQL).  

	Finally, let's go back to ~picasso/release/src.  The Makefile here
compiles the complete picasso system, using the pcl-clx dump generated in
sys.  This uses the widgets and toolkit subdirectories (which contain
picasso sources) under the control of the sysdef.cl file that describes the
picasso system to PDS.  

2.  Compiling Picasso

	Here is the sequence for compiling Picasso on any machine (it is
assumed that all machines have access to the picasso source tree, we
recommend NFS to avoid the overhead of duplicated sources).

	a.  Making the pcl-clx dump
	    i.	To compile this dump for the first time:

			cd ~picasso/release/src/sys
			make pcl-clx

	    ii. to recompile some packages, use make compile-<package> and
		the make load (to put all selected packages into a new dump).

	b.  Making the picasso dump
	    i.  "make picasso" will always compile just the needed files and
		create a new dump.  If a recompilation of pcl-clx requires
		recompiling all of picasso from scratch, "make clean" and then
		"make picasso" (this is only needed if a macro change in CLX
		or PCL affects picasso).

3.  Running Picasso

	You probably would like to try some of the tools we've provided, and
then start writing your own.  To run a picasso tool:

	Start picasso (just type "picasso" to the shell if your path is correct)
	<picasso> (run-tool-named <tool-name>)

The following tools are available for you to run:

	'("paper" "demo" . "tool")
	'("fmtool" "tool")
	'("form-test" "tool")
	'("test" "tool")

To add your own tools,  create the appropriate subdirectory in ~picasso/lib/po.

We hope to have more tools available fo you to try shortly, we will send 
updates to the picasso-users mailing list.

6.  Questions/Mailing List

	As indicated in the README file, we ask that you send your name,
address, and electronic mail address to us at
picasso-list@postgres.Berkeley.EDU if you decide to install Picasso.  Please
tell us if you would like to be put on the picasso-users mailing list.  You
can send mail to that list at picasso-users@postgres.Berkeley.EDU or to us
at picasso-help@postgres.Berkeley.EDU.  Please send bug reports to
picasso-bugs@postgres.Berkeley.EDU.  

7.  Mailing Address

	Should you wish to contact us by paper mail, please address 
	correspondence to:

	Picasso Project
	c/o Professor Lawrence A. Rowe
	Computer Science Division
	571 Evans Hall
	University of California
	Berkeley, CA   94720


8.  NOTES ON THIS VERSION

a.  The MIPS implementation is untested
b.  Due to a minor bug, DISPLAY variables of the form "unix:0.0" are not
    accepted.  Instead, use "machname:0.0"
