Here is the preliminary plan for staging the equipment we intend to show at the SIGPLAN/SIGSOFT conference in Seattle. The goal is to establish and run the configuration at PARC beforehand. All the equipment can then be shipped together from the PARC loading dock.
The staging area will be the open area in the Purple Lab, room 35-2403 (the room with the Color Versatec plotter; we will use the open space near the power distribution panels). OSD should deliver their equipment to this area. A critical resource will be the 10-mbit Ethernet cable which we could use as early as possible, since the Cedar configuration piggy-backs its Grapevine and boot servers from the 10-mbit Ethernet.
We expect the following OSD equipment: 10-mbit Ethernet cable, 3 workstations, 1 file server, 1 print server, and 1 Librarian/Adobe server.
We expect the following CSL Cedar equipment: 3-mbit Ethernet cable, 3 Dorados, 1 DLion Grapevine server, 1 DLion boot server/gateway, 1 Dicentra gateway.
The Seattle demo configuration will be a combined Cedar/XDE internet. The Cedar Dorados will be on their own 3-mbit mini-Ethernet; the XDE workstations and servers will be on a 10-mbit Ethernet; and the Cedar Grapevine and boot server will be on the XDE 10-mbit Ethernet. A Dicentra will provide the gateway between the 3-mbit and 10-mbit Ethernets.
For the staging at PARC, the 10-mbit Ethernet will be entirely within 2403, while the 3-mbit Ethernet will stretch from the staging area to the server room (so we don't have to move the Dorados due to their special power requirements), a distance of about 40 feet. A temporary Dicentra gateway will be used to connect the 3-mbit mini-Ethernet to PARC net 3# in the Purple Lab server room. This permits the Dorados to be useable within CSL whenever we are not testing the demo configuration. To isolate the demo configuration, the temporary gateway is disconnected.
Action items:
Becky Sarranzin: please arrange for OSD to ship the 10-mbit Ethernet cable and equipment to 35-2403. Please let me know when the remainder of the equipment could be delivered.
Mike Overton/Hal Murray: please arrange the 3-mbit mini-Ethernet and temporary gateway. Initial Dorado allocation for the mini-Ethernet are Shangrila, Sea-Horse, and Reprisal (I think all three are 4MW, 315 disk, color, PC board Dorados located in the Purple Lab server room).
17-Jun-85 To: Pier SIGPLAN Travel Plans
Date: 17 Jun 85 11:23:42 PDT From: Pier.pa Subject: SIGPLAN Travel Plans To: Pier
Depart Monday, June 24, from SFO on AirCal #765, departing 5 PM arriving 6:49 PM
Return Friday, June 28, from SEATAC on AirCal #724, departing 4:45 PM arriving 6:58.
In-reply-to: "My message of 21 Jun 85 20:05:39 PDT"
To: Pier
Cc: Spreitzer
My first message had a bug in it: failing to start EQT (part of the statement interpreter). Here's a corrected version:
A possibly fun script of things to do with ViewRec might include making RecordViewers on the Rope, IO, and FS interfaces (this makes incidental use of the statement interpreter):
Do out.GetInfo, PutRope, PutChar, Flush, EraseChar
Do in.GetInfo, EndOf, CharsAvail, PeekChar, GetChar, Backup, GetCedarTokenRope, GetInt, GetReal, GetRopeLiteral, SkipWhitespace, others that work (GetUnpackedTime doesn't)
N.B.: &vio.in is an edited stream
Don't worry about things that fail --- most of them you can simply abort. I think the worst you can do is close a stream --- and to fix that you can simply create a new one and start over.
Demo the FS interface:
Bind the BasicTime.GMT's, because ViewRec doesn't have default handling for TYPE[2]'s:
Do ExpandName, ConstructFName, FileInfo, Copy, Delete, Rename, SetKeep
22-Jun-85 Spreitzer.pa PolyHack script
Date: 22 Jun 85 00:51:27 PDT
From: Spreitzer.pa
Subject: PolyHack script
To: Pier.pa
Cc: Spreitzer
The PolyHack is a graphics hack that uses BiScrollers, ViewRec, StructuredStreams, and Misp.
Read the PolyHack document for an introduction to the theory of the PolyHack, and details of how to use it.
There is a bit of an embarrasment here --- the introducion of a second language (Misp), when the first (Cedar) would do (nearly) as well. The real reason it uses Misp, instead of the interpreter (including the statement interpreter), is that when the PolyHack was created, the interpreter was less powerful than Misp in a number of relevant ways. The interpreter has since gotten better, but is still a bit less powerful: it cannot pass functions that it created around as values; that feature is used in a few things I've tried in the PolyHack, but will not be used in the script below.
My favorite configuration of viewers is: (column division in the middle), "(BiScrolling) Poly Hack" above "(BiScrolling) Poly Hack Control" in the left column, and "Watch" above this script above "PolyHacks" [possibly above "(BiScrolling) Poly Hack Log" adjusted small] in the right column.
Some Tachys:
Set sweep mode, select old Tachy in "PolyHacks", middle click in "(BiScrolling) Poly Hack", then left click (now it starts running), then right click (when bored).
Same for new Tachy.
Some Sins:
Set fill mode. Select the do loop from the Sins section of "PolyHacks", and hit the ReadEvalPrint button in the control panel. This runs a demo that repeatedly chooses a random pattern and runs it through one cycle. Any click in the graphics window to stop.
Some Polygons:
Set outline mode. Select the do loop from the Polygons section of "PolyHacks", and hit the ReadEvalPrint button in the control panel. This runs a demo that is similar to an XDE DMT. Middle click in the graphics window to stop.
Some Spirographs:
Get color viewers going, and put the "(BiScrolling) Poly Hack" in the color column. Make sure the colormap actually has interesting colors in it (not just all grays).
Set trace mode.
Select the red, green, and blue example from the Spirographs section of "PolyHacks", middle click in "(BiScrolling) Poly Hack", then left click (now it starts running), then right click (when completed). Try it this one with sweep mode. You might try composing some traditional (two wheeled) spirographs --- there are some relatively trivial examples in "PolyHacks".
22-Jun-85 Spreitzer.pa Background picture demo
Date: 22 Jun 85 01:06:47 PDT
From: Spreitzer.pa
Subject: Background picture demo
To: Pier.pa
Cc: Spreitzer
Here's a hack Bill Jackson pushed through: setting the background color to be a sampled color, instead of the usual desktop-gray stipple.
Below is given a way to use any AIS file as the background color. Also given is a way to extract AIS files from press files. See if you can find any good files to use.
Note the phase problem when area revealed from behind icons is painted. Perhaps it would be interesting to try adding scaling and translation to the transformation used so that this problem isn't apparant.
The PressFileUtilities package exports a way to extract the sampled images from press files and put them in AIS files.
-- Do out.GetInfo, PutRope, PutChar, Flush, EraseChar
-- Do in.GetInfo, EndOf, CharsAvail, PeekChar, GetChar, Backup, GetCedarTokenRope,
-- GetInt, GetReal, GetRopeLiteral, SkipWhitespace, others that work (GetUnpackedTime doesn't)
-- N.B.: &vio.in is an edited stream
-- Don't worry about things that fail most of them you can simply abort. I think the worst you can do is close a stream and to fix that you can simply create a new one and start over.
--
Demo the FS interface:
-- Bind the BasicTime.GMT's, because ViewRec doesn't have default handling for TYPE[2]'s:
-- Do ExpandName, ConstructFName, FileInfo, Copy, Delete, Rename, SetKeep
22-Jun-85 Plass.pa Viewers for Cedar 6.0
Date: 22 Jun 85 11:19:29 PDT From: Plass.pa Subject: Viewers for Cedar 6.0
To: Release Coordinator <Atkinson.pa>
Cc: CedarImplementors^.pa
Reply-to: Plass.pa
Viewers
I borrowed the Viewers torch to make a small fix to ViewerPaintImpl. The desktop colors now tile properly; if "Foo.ais" is a bitmap AIS file (e.g., one created with PressScreen), say
and your desktop will be less boring. (You can use any Imager color, but this is a fast case. There is another variable for the color display).
22-Jun-85 To: Beach PolyHack Demo for Seattle
Date: 22 Jun 85 15:33:53 PDT From: Pier.pa Subject: PolyHack Demo for Seattle To: Beach Reply-To: Pier cc: , Pier
The PolyHack is a graphics hack that uses BiScrollers, ViewRec, StructuredStreams, and Misp.
Read the PolyHack document for an introduction to the theory of the PolyHack, and details of how to use it.
There is a bit of an embarrasment here --- the introducion of a second language (Misp), when the first (Cedar) would do (nearly) as well. The real reason it uses Misp, instead of the interpreter (including the statement interpreter), is that when the PolyHack was created, the interpreter was less powerful than Misp in a number of relevant ways. The interpreter has since gotten better, but is still a bit less powerful: it cannot pass functions that it created around as values; that feature is used in a few things I've tried in the PolyHack, but will not be used in the script below.
-- close all viewers on desktop then open in this order:
Left column: (BiScrolling) Poly Hack, (BiScrolling) Poly Hack Control, MispInterpreter, PolyHack.PreLoad. Shove PreLoad contents into MispInterpreter. Close MispInterpreter and PreLoad.
Right column: Watch, this script, PolyHacks
-- Some Tachys:
Set sweep mode, select old Tachy in "PolyHacks", middle click in "(BiScrolling) Poly Hack", then left click (now it starts running), then right click (when bored).
Same for new Tachy.
-- Some Sins:
Set fill mode. Select the do loop from the Sins section of "PolyHacks", and hit the ReadEvalPrint button in the control panel. This runs a demo that repeatedly chooses a random pattern and runs it through one cycle. Any click in the graphics window to stop.
-- Some Polygons:
Set outline mode. Select the do loop from the Polygons section of "PolyHacks", and hit the ReadEvalPrint button in the control panel. This runs a demo that is similar to an XDE DMT. Middle click in the graphics window to stop.
-- Some Spirographs:
Get color viewers going, and put the "(BiScrolling) Poly Hack" in the color column. Make sure the colormap actually has interesting colors in it (not just all grays).
Set trace mode.
Select the red, green, and blue example from the Spirographs section of "PolyHacks", middle click in "(BiScrolling) Poly Hack", then left click (now it starts running), then right click (when completed). Try it this one with sweep mode. You might try composing some traditional (two wheeled) spirographs --- there are some relatively trivial examples in "PolyHacks".