Catalog.tioga
Copyright © 1985 by Xerox Corporation. All rights reserved.
Russ Atkinson (RRA) November 12, 1985 11:23:39 am PST
CEDAR CATALOG
CEDAR CATALOG
CEDAR 6.0 — FOR INTERNAL XEROX USE ONLY
CEDAR 6.0 — FOR INTERNAL XEROX USE ONLY
Cedar Catalog
Version 6.0
Release as: [Indigo]<Cedar6.0>Documentation>Catalog.tioga

© Copyright 1984, 1985 Xerox Corporation. All rights reserved.
Abstract: This catalogue is a list of "interesting" Cedar packages and tools. Each component is described by a maintainer-supplied entry.
In general, all the source, bcds and other files relevant to a package named X can be gotten through the file [Indigo]<Cedar6.0>Top>X.df.
[If you are reading this document on-line, we suggest that you use the Tioga Levels and Lines menus to initially browse the top levels.]
XEROX  Xerox Corporation
   Palo Alto Research Center
   3333 Coyote Hill Road
    Palo Alto, California 94304

For Internal Xerox Use Only
Introduction
Note that Cedar6.0 supports pseudo-servers, so [Cedar] is used to denote the server that contain files pertaining to the release. For non-Cedar6.0 users, substitute [Cyan] for [Cedar] where necessary.
Note that many packages formerly in Cedar are now in CedarChest. The file name conventions for CedarChest are the same for Cedar, so [Cedar]<CedarChest6.0> contains files compatible with the files in [Cedar]<Cedar6.0>.
In general, all the source, bcds and other files relevant to a Cedar package named X can be gotten through the file [Cedar]<Cedar6.0>Top>X.df. The way to obtain the files necessary to run package X is to use the command
Bringover -p [Cedar]<Cedar6.0>Top>X.df
The documentation directory is [Cedar]<Cedar6.0>Documentation> unless otherwise specified.
Complaints are the precursors of improvement. Please send suggestions for improving the form or content of this Catalog to CedarSupport^.pa. Send comments about any particular entry to its maintainer, with copies to CedarSupport^.pa.
Cedar System Structure
The Cedar system has two levels: Nucleus, which is the level of Cedar required for loading and running programs, and Life Support, which is the level of Cedar necessary for program development. The Life Support level contains the Nucleus level, but has few "creature comforts." The region outside of Life Support (but inside Cedar) contains many user-accessible tools and interesting packages.
Nucleus
The Nucleus may be thought of as the kernel of the operating system for Cedar. It provides low-level access to devices such as the display (Terminal), disk (Disk), and Ethernet (Communication, Pup). The Nucleus also provides virtual memory support (VM), a file system (File, FS), and basic stream facilities (IO, STP). The Nucleus also provides the basic support necessary for loading and running programs (BasicLoadState, Loader, LoadState, MesaRuntime). The components in the Nucleus (and in the BasicCedar*.boot files) are:
BasicLoadState, BasicTime, BcdStuff, BTree, CedarRuntime, Communication, Disk, File, FileStream, FormatDisk, FS, GrapevineUser, HeadsCommon, HeadsD0, HeadsDorado, Iago, IO, Loader, LoadState, MesaRuntime, ProcessProps, Pup, Real, Rollback, Rope, SafeStorage, SimpleTerminal, STP, Tentacles, Terminal, UserCredentials, VM
Life Support
The Life Support level of Cedar includes the Nucleus level, and adds more sophisticated packages and tools. It provides user interaction facilities such as a screen manager (TIP, Viewers), a text editor (Tioga), and command and expression interpreters (CommandTool, InterpreterTool). Program creation and management tools are also included (Binder, Compiler, DFTool).
The components loaded by Basic.Loadees, but not in Nucleus, are:
AMEvents, AMModel, AMProcess, AMTypes, BasicPackages, ColorPackage, CommandTool, ComputeServerUser, DebugTool, DFCommands, DFPackage, EditTool, Idle, Imager, Inscript, Installer, Interpreter, InterpreterTool, PrintTV, ReadEvalPrint, Rosary, RPCRuntime, Tioga, TIP, TJaM, TRope, UserProfile, VersionMap, ViewerIO, Viewers, Watch, WorldVM
Other components of the Life Support level are:
Binder, BootTool, Chat, Clock, Compiler, DebugTool, DFTool, Watch
Release Components
In general, documentation for component name is stored on one of:
[Cedar]<Cedar6.0>name>*.mesa -- when the interface is the best documentation
[Cedar]<Cedar6.0>Documentation>name.tioga
but there are occasional exceptions. For brevity, we do not list Component.Press if Component.Tioga exists, and we do not include [Cedar]<Cedar6.0>Documentation> or [Cedar]<Cedar6.0>name> in the file name if that is the prefix. If not specified, the host is assumed to be [Cedar].
Unless otherwise indicated, questions about changes in individual components should be addressed to their maintainers.
AMEvents
DF files: AMEvents.df
Documentation: AMEvents.mesa, FastBreak.mesa | see maintainer
Maintainer: CedarSupport^.pa
AMEvents is the part of the Cedar abstract machine concerned with interaction between executing programs and the debugger: uncaught signals, breakpoints, and interpreted procedure calls. Normal access to these facilities is through the InterpreterTool. Consult a wizard before calling AMEvents directly.
AMModel
DF files: AMModel.df
Documentation: AMModel.mesa, AMMiniModel.mesa
Maintainer: CedarSupport^.pa
AMModel.df includes the components of the Cedar "abstract machine" that deal with loaded programs, frames, their object modules and source modules, and interdependencies. Its major public interfaces are AMModel.mesa and AMMiniModel.mesa.
AMProcess
DF files: AMProcess.df
Documentation: AMProcess.mesa | see maintainer
Maintainer: CedarSupport^.pa
AMProcess is the component of the Abstract Machine that manipulates processes. CedarProcess is a usefuul adjunct for safely performing an action with a given priority, and for safely waiting for the results of forked processes (avoiding the unsafe constructs Process.Detach, FORK and JOIN).
AMTypes
DF files: AMTypes.df
Documentation: AMTypes.mesa, AMBridge.mesa
Maintainer: CedarSupport^.pa
AMTypes.df includes the part of the Cedar "abstract machine" that deals with types, values and variables. Its major public interfaces are AMBridge.mesa and AMTypes.mesa.
BasicLoadState
DF files: BasicLoadState.df
Documentation: see maintainer
Maintainer: CedarSupport^.pa
The lowest level of load state support. This is necessary for building the rest of the load state upon, but is not normally used by itself.
BasicPackages
DF files: BasicPackages.df
Documentation: BasicPackagesDoc.tioga
Maintainer: CedarSupport^.pa
BasicPackages combines several small components of general utility, including the trace-and-sweep garbage collector. The interfaces of note are:
Commander - provides a central command registry that is used by most programs with text commands (as contrasted with tools that provide interaction through viewers). The registry is monitorized to allow concurrent access.
PriorityQueue - A PriorityQueue object is a collection of items where items can be inserted in any order, and removed in best-first order, where "best" is determined by a user-supplied predicate. This package can be used to sort in O(N log N) time. Each priority queue is monitorized to allow concurrent access.
Random - provides random number streams. Each Random stream is monitorized to allow concurrent access.
RedBlackTree - provides a sorted table abstraction with average log N insertion or deletion time. Each RedBlackTree table is monitorized to allow concurrent access.
RefTab - provides an alternative to property lists for associating information with unique keys in a -global fashion using specific structures (hash tables). RefTab includes procedures for creating a new table, fetching a value for a particular key, storing a new key-value pair, deleting a key-value pair, and enumerating the pairs in a given table.
RopeFile - is a module that implements ropes backed by files. The ropes need not take up much virtual memory, which can either improve or degrade performance, depending on the pattern of Rope operations used.
RopeList - is similar to List, but operates on objects of type LIST OF ROPE. No monitorization is provided.
SymTab - provides symbol table objects, which can be used to associate ropes with REFs. SymTab has insertion, lookup, deletion, and enumeration operations. Each SymTab object is monitorized to allow concurrent access.
BasicTime
DF file: BasicTime.df
Documentation: BasicTime.mesa | see maintainer
Maintainer: CedarSupport^.pa
BasicTime provides access to the various kinds of system-maintained time, such as time of day and high resolution time. Conversions to and from Pup (Alto) time format and NS (product standard) time formats are provided.
BcdStuff
DF file: BCDStuff.df
Documentation: see maintainer
Maintainer: CedarSupport^.pa
Basic support for BCD file manipulation.
Binder
DF file: Binder.df
Documentation: Mesa 5.0 language manual (outdated)
Maintainer: CedarSupport^.pa
The Mesa Binder.
BootTool
DF file: BootTool.df
Documentation: see maintainer
Maintainer: CedarSupport^.pa
This tool provides a means to checkpoint or rollback, or to boot other volumes using button clicks. For those with special needs, a more elaborate tool is provided to support booting different files, or booting with unusual parameters. The booting switches are:
0 - worry-call debugger as early as possible
1 - call debugger after MesaRuntime initialization
2 - call debugger after VM initialization
3 - call debugger after File initialization
4 - call debugger after finding VM file and swapping in non-initial parts of boot file
5 - call debugger in LoaderDriver after loading but before starting loadees
A - don't start Ethernet1 drivers
B - don't start Ethernet2 drivers
C - don't start Communication package
D - development version: (not currently used)
F - do full booting sequence, even if defaults would imply a rollback
H - hang in CPU loop with MP code instead of swapping to debugger
I - enable control-swat as early as possible (instead of waiting until after login)
L - long (and interactive) installation dialogue
N - don't touch the disk during initialization (forces entry to Iago)
P - don't read user profile from disk
Q - quick boot; don't examine DF files during booting
R - rollback if the system volume has a valid checkpoint
S - use Software for reference-counting, not microcode
T - force teledebugging instead of disk world-swap
V - perform VM copying for checkpoint (internal use only!)
W - for world-swap debugger, assume debuggee outload file is valid/interesting
BTree
DF file: BTree.df
Documentation: BTreeDoc.tioga
Maintainer: CedarSupport^.pa
This Cedar package maintains an ordered collection of objects as a BTree. The objects may be of different sizes, and there may be a large number of them (tens or hundreds of thousands). The amount of virtual memory required does not depend on the size of the BTree, and the cost of finding, inserting, and deleting objects increases only very slowly as the BTree gets larger. The package makes very few assumptions about the representation of the objects being stored or about the properties of the storage itself.
BTreeSimple
DF file: BTreeSimple.df
Documentation: BTreeSimple.mesa
Maintainer: CedarSupport^.pa
This is a substantially simplified interface to the BTree package, suitable for clients not requiring the full flexibility of the Cedar BTree interface. In particular, the representation of a BTree entry is fixed by this package (a text key and a sequence value); and the BTree is backed up on an FS (or AlpineFS) file. In return for this loss of flexibility, the package takes care of most of the required boilerplate and bookkeeping automatically.
Chat
DF file: Chat.df
Documentation: ChatDoc.tioga
Maintainer: CedarSupport^.pa
Tool for talking to file servers. A command line of simply "Chat" will create an iconic Chat viewer. A command line like "Chat maxc" will create an open chat viewer, connect to Maxc, and log in the current Cedar user.
Clock
DF file: Clock.df
Documentation: see maintainer
Maintainer: Atkinson.pa
Clock is a graphic display of the current time. It uses Graphics and Viewers to present a circular clock face with hands. It is a good example program as well as an attractive timepiece. The ChangeOffset button now changes the time by hours (left-click), minutes (middle-click) or seconds (right-click). Holding the SHIFT key during the mouse click causes the time to appear to go forward, otherwise time appears to go backward. Holding CTRL for any click causes the displayed time to be the actual time.
CommandTool
DF file: CommandTool.df
Documentation:
CommandToolDoc.tioga, CommandToolCommands.tioga |
CommandTool.mesa, FileNames.mesa
Maintainer: CedarSupport^.pa
The CommandTool is a stream-oriented "glass teletype" command-line processor. It is a place to invoke Cedar subsystems. It is sufficiently like any other executive so that you can probably get by, but you should read CommandToolDoc.tioga and some of the documentation files for the various commands.
Interesting interfaces:
CommandTool.mesa -- command line parsing and so forth.
FileNames.mesa -- processing of file names beyond that available from FS
Communication
DF file: Communication.df
Documentation: see maintainer
Maintainer: CedarSupport^.pa
The Pilot communication package implements the basic communication protocols - up to the level of byte streams. There are two flavors of protocol available: "OISCP," described in the Pilot Programmers' Manual, and "PUP." At present, only the PUP protocols are used within CSL. These are all "unsafe" interfaces. See also the STP package for FTP transfers, and Lupine for remote procedure calls.
Compiler
DF file: Compiler.df
Documentation: Mesa 5.0 language manual (outdated) | Cedar Language Reference Manual
Maintainer: CedarSupport^.pa
The Cedar language compiler.
ComputeServerUser
DF file: ComputeServerUser.df
Documentation: see maintainer
Maintainer: Hagmann
This is a minimal package for supporting the Summoner (aka ComputeServer).
DebugTool
DF file: DebugTool.df
Documentation: DebugToolDoc.tioga | see maintainer
Maintainer: CedarSupport^.pa
The DebugTool is the means for debugging remote machines, or for manipulating processes on your local machine. It is not especially reliable.
Dependencies
DF file: Dependencies.df
Documentation: Dependencies.mesa
Maintainer: CedarSupport^.pa
Dependencies implements a single command
Dependencies fileName
which creates an object file dependency listing (with Tioga formatting, no less!) that describes which object files depend on which other object files. The fileName is taken to be a DF file, and the output listing goes to fileName.depends.
DFCommands
DF file: DFCommands.df
Documentation: BringOverDoc.tioga, SModelDoc.tioga, VerifyDFDoc.tioga
Maintainer: CedarSupport^.pa
DFCommands provides a command-line interface to the DFTool. These commands (BringOver, SModel, VerifyDF) do not interact with the user; that is, in terms of Cedar 4.4's versions of these commands, "/a" is now the only behavior available.
DFIncludes
DF file: DFIncludes.df
Documentation: in catalog entry
Maintainer: CedarSupport^.pa
The command line "DFIncludes XXX.df" produces a file DFIncludes.txt with lines of the form "shortFileName containingDfFile directory", sorted by shortFileName. There is one line for each source file included (in the DF sense) in XXX.df. Both containingDfFile and directory are stripped of redundant information (like "/Cedar/Cedar6.0/Top/") to keep the lines short. Warnings are written to DFIncludes.log.
DFPackage
DF file: DFPackage.df
Documentation: see maintainer |
DFOperations.mesa, DFOperationsQueue.mesa, DFUtilities.mesa
Maintainer: CedarSupport^.pa
DFPackage is the basic Cedar support for reading and writing DF files.
DFTool
DF file: DFTool.df
Documentation: DFToolDoc.tioga | see maintainer
Maintainer: CedarSupport^.pa
DFTool provides an interactive tool for BringOver, SModel, and VerifyDF commands.
Disk
DF file: Disk.df
Documentation: Disk.mesa | see maintainer
Maintainer: CedarSupport^.pa
Basic Disk support.
EditTool
DF file: EditTool.df
Documentation: TiogaDoc.tioga (via Tioga.df)
Maintainer: TiogaImplementors^.pa
EditTool, formerly included under Tioga.df, is now a separate package. In addition to the EditTool itself, EditTool.df describes a collection of Tioga executive commands.
EssentialStyles
DF file: EssentialStyles.df
Documentation: see individual style files, TiogaDoc.Tioga, or SampleSheet.Tioga
Maintainer: Beach
This DF file consolidates the essential Tioga style files needed to use Cedar.
Obsolete styles (Default.Style, Mesa.Style, and BasicLooks.Style) are included in this DF file but will be eliminated in some future release (when we can recompile all of the Cedar interface files after changing their styles)..
ExtraIago
DF file: ExtraIago.df
Documentation: ExtraIagoDoc.tioga
Maintainer: <Willie-Sue> Orr
ExtraIago is a set of commands in addition to the normal Iago commands that lets you do interesting things with your disk. Novices beware!
File
DF file: File.df
Documentation: File.mesa | see maintainer
Maintainer: CedarSupport^.pa
The basic file support underlying FS. No user-servicable parts.
FileStream
DF file: FileStream.df
Documentation: FileStreamDoc.tioga
Maintainer: Hagmann
FileStream a generic file stream package, and currently its clients are FS and Alpine file streams. No user-servicable parts.
FormatDisk
DF file: FormatDisk.df
Documentation: FormatDisk.mesa
Maintainer: CedarSupport^.pa
Performs machine-dependent disk initialization operations, principally formatting and initial microcode installation. Iago is the only intended client. Novices beware!
FS
DF file: FS.df
Documentation: FSDoc.tioga (out of date)
Maintainer: CedarSupport^.pa
FS is a file system for use on a Cedar workstation. It provides access both to remote file servers and to the local disk. Remote files accessible from FS must reside on a file server that supports the FTP protocol, in particular IFS's and Alpine servers. These file servers may be accessed from many Cedar instances on different workstations at the same time. Local files are accessed through an abstraction called the local server. The local server is the set of logical volumes on the local disk of a Cedar instance. One of these logical volumes may be designated the system volume. FS provides a directory for each volume, and a cache for remote files on the system volume.
FS also defines a generic abstraction, the FS.OpenFile, of which the workstation file system is only one class. The generic operations provide access to the data pages and properties of files. Other packages may create their own classes of FS.OpenFile's, upon which these generic FS operations also may be performed. For example, direct page-at-a-time access to Alpine servers is provided through this mechanism.
FS also contains facilities for creating IO.STREAM's on files, for binding local names to remote files, for finding the version of a file that was created at a particular time, and for limiting the number of extant versions of local files.
Germ
DF file: Germ.df
Documentation: see maintainer
Maintainer: CedarSupport^.pa
The Germ is that small piece of code that runs during teledebugging, rollback, checkpoint or world-swap. Normal users should not be aware of it.
GrapevineUser
DF file: GrapevineUser.df
Documentation: see maintainer
Maintainer: CedarSupport^.pa
GrapevineUser is the package for interfacing to the Grapevine mail and registration services. The Cedar interfaces to Grapevine are GVBasics.mesa, GVNames.mesa, GVSend.mesa and GVRetrieve.mesa. GrapevineUser is included in the Cedar boot file.
GVMail
DF file: GVMail.df
Documentation: GVMail.mesa
Maintainer: Willie-Sue.pa
This component contains common mail parsing routines for Walnut and Peanut.
HeadsCommon
DF file: HeadsCommon.df
Documentation: see maintainer
Maintainer: CedarSupport^.pa
Common device drivers.
HeadsD0
DF file: HeadsD0.df
Documentation: see maintainer
Maintainer: CedarSupport^.pa
Dolphin-specific device drivers.
HeadsDLion
DF file: HeadsDLion.df
Documentation: see maintainer
Maintainer: CedarSupport^.pa
Dandelion-specific device drivers.
HeadsDorado
DF file: HeadsDorado.df
Documentation: see maintainer
Maintainer: CedarSupport^.pa
Dorado-specific device drivers.
Iago
DF file: Iago.df
Documentation: see maintainer
Maintainer: CedarSupport^.pa
The Cedar replacement for Othello. This tool manages physical and logical volumes on the local system disk.
Idle
DF file: Idle.df
Documentation: Idle.mesa | see maintainer
Maintainer: CedarSupport^.pa
Low-level support for putting Cedar to sleep.
IFSFile
DF file: IFSFile.df
Documentation: IFSFile.mesa | see maintainer
Maintainer: CedarSupport^.pa
IFSFile supports Leaf protocol access to IFS. Leaf access is primarily useful for low overhead random access to pages of a file. There are no functional changes since Cedar 4.4, although there is a greater use of SafeStorage facilities.
Imager
DF file: Imager.df
Documentation: ImagerDoc.tioga
Maintainer: ImagerImplementors^.pa
The Imager is the standard means for drawing text, graphics, or sampled images. In Cedar 6.0 Imager replaces the old Graphics package.
Inscript
DF file: Inscript.df
Documentation: InscriptDoc.tioga
Maintainer: CedarSupport^.pa
The basic keyboard input subsystem.
Installer
DF file: Installer.df
Documentation: see maintainer
Maintainer: CedarSupport^.pa
Provides support for determining the profile, for bringovers of necessary files and fonts, and other necessary stuff during a full boot.
Interpreter
DF file: Interpreter.df
Documentation: Interpreter.mesa
Maintainer: CedarSupport^.pa
The programming interface to the Cedar/Mesa expression interpreter. It is used by the InterpreterTool and by the "←" command.
InterpreterTool
DF file: InterpreterTool.df
Documentation: InterpreterToolDoc.tioga
Maintainer: CedarSupport^.pa
The user interface to the Cedar/Mesa expression interpreter.
IntervalTimer
DF file: IntervalTimer.df
Documentation: IntervalTimer.tioga
Maintainer: Swinehart.pa
Some applications need to deal with shorter or more precise timing intervals than the Process interface provides. This package permits any process to wait for a specified number of basic system clock pulses, expressed either in microseconds or pulses. The package is available only on the Dorado.
IO
DF file: IO.df
Documentation: IODoc.tioga, EditedStream.mesa, IOClasses.mesa
Maintainer: CedarSupport^.pa
The IO component exports the IO, EditedStream, IOClasses, IOUtils, and Convert interfaces. The first four interfaces define the STREAM type and the generic operations on streams, contain procedures for creating streams from objects of other types, and provide stream-oriented scanning and printing. The Convert interface gives input/output conversions between several Cedar types and both ROPE and REF TEXT.
LFBoundingBox
DF file: LFBoundingBox.df
Documentation: LFBoundingBoxDoc.tioga
Maintainer: Plass
Provides a user interface for clients that want a user-defined rectangular portion of the screen.
Lister
DF file: Lister.df
Documentation: ListerDoc.tioga
Maintainer: Atkinson.pa
Lister is a program to produce human readable files from bcd files produced by the Compiler and Binder. Lister registers a variety of commands, each of which produces a different set of information from a given list of bcd files. These commands include:
BcdLister lists contents of a bcd file
BodyLister lists the bodies of a bcd file (single module)
CodeLister lists the code of a bcd file (single module)
ExportsLister lists the exports of a bcd file
FGTLister lists the fine grain table of a bcd file (single module)
GlobalFramesLister lists the fine grain table of a bcd file
RTBcdLister lists the runtime types information of a bcd file
SymbolLister lists the symbols of a bcd file (single module)
UnboundLister lists the unbound exports of a bcd file
UsingLister generates a DIRECTORY clause for a bcd file (single module)
Loader
DF file: Loader.df
Documentation: Loader.mesa | see maintainer
Maintainer: CedarSupport^.pa
The basic program loader. Also provides operations for pinning code and/or global frames.
LoadState
DF file: LoadState.df
Documentation: LoadState.mesa | see maintainer
Maintainer: CedarSupport^.pa
This DF describes the software necessary to maintain and access the Cedar load state. Most clients should use AMModel instead of this level.
Lupine
DF file: Lupine.df
Documentation: LupineUsersGuide.press
Maintainer: CedarSupport^.pa
Lupine is a program that allows you to make inter-machine "Remote Procedure Calls" ("RPC"). This allows you to write what look like ordinary Mesa procedure calls to invoke operations on another machine on the Pup internet. Lupine and its supporting RPCRuntime are intended to make network communication very easy, very fast, and very cheap. Secure communication facilities are included.
Maintain
DF file: Maintain.df
Documentation: see maintainer
Maintainer: CedarSupport^.pa
Maintain provides a tool for interrogating and updating the Grapevine registration database.
MakeBoot
DF file: MakeBoot.df
Documentation: see maintainer
Maintainer: CedarSupport^.pa
MakeBoot is the program used to make boot files and germ files.
MesaRuntime
DF file: MesaRuntime.df
Documentation: see maintainer
Maintainer: CedarSupport^.pa
Runtime support for the Mesa language. Exports these interfaces: Basics, MesaRuntimeInit, PrincOps, PrincOpsUtils, Process, ProcessExtras, RuntimeError.
MicrocodeD0
DF file: MicrocodeD0.df
Documentation: see maintainer
Maintainer: Fiala.pa
This component consists of microcode files that Dolphin users must install on their disk in order to run Cedar. The installation is ordinarily done automatically by Iago when you create your Cedar world. If you issue the Iago commands manually, the files you install are:
Install Cedar Microcode: CedarD0.eb
Install Initial Microcode: InitialPilot.eb
If you want to boot Cedar with the boot button, OR
Install Initial Microcode: RubiconInitialAltoD0.eb
If you want to boot the Alto emulator with the boot button.
MicrocodeDLion
DF file: MicrocodeDLion.df
Documentation: see maintainer
Maintainer: Fiala.pa
MicrocodeDLion contains Dandelion microcode support for Cedar.
MicrocodeDorado
DF file: MicrocodeDorado.df
Documentation: [Cedar]<DoradoDocs>DoradoBooting.press
Maintainer: Willie-Sue.pa
This component consists of microcode files that Dorado users must install on their disk in order to run Cedar. The installation is ordinarily done automatically by Iago when you create your Cedar world. If you issue the Iago commands manually, the files you install are:
Install Cedar Microcode: file CedarDorado.eb
Install Initial Microcode: file InitialEtherCedarDorado.eb
If you want to boot Cedar with the boot button, OR
Install Initial Microcode: file InitialEtherAltoMesaDorado.eb
If you want to boot the Alto emulator with the boot button.
PGS
DF file: PGS.df
Documentation: PGS.tioga
Maintainer: CedarSupport^.pa
The parser generator system (PGS) is a Mesa program which takes a context free grammar specified in Backus-Naur form as input and tests whether it is LALR(1); if the LALR(1) condition is satisfied, compacted binary tables are output which can be used in conjunction wth the Mesa parser. Ancillary tables are also output which simplify the writing of lexical routines to recognise the terminal symbols of the grammar. As a primary task of the PGS is to aid development the Mesa system itself a preprocessor is included which aids this.
PressReader
DF file: PressReader.df
Documentation: see maintainer
Maintainer: Plass.pa
A client interface for reading press files.
PrintTV
DF file: PrintTV.df
Documentation: PrintTV.mesa, BackStop.mesa
Maintainer: CedarSupport^.pa
PrintTV provides for textual output of Abstract Machine values.
ProcessProps
DF file: ProcessProps.df
Documentation: ProcessProps.mesa
Maintainer: Atkinson.pa
ProcessProps provides a safe association of <key, value> pairs with processes. It is similar to LISP-style dynamic binding.
Pup
DF file: Pup.df
Documentation: see maintainer
Maintainer: CedarSupport^.pa
This implements the basic PUP communication protocols - up to the level of byte streams. Most public interfaces are in Communication.df, but EFTP is in Pup.df. Higher level protocols are available through the STP package (for file transfer) and Lupine (for remote procedure calls).
ReadEvalPrint
DF file: ReadEvalPrint.df
Documentation: ReadEvalPrint.mesa | see maintainer
Maintainer: CedarSupport^.pa
ReadEvalPrint provides a framework for programs that interactively execute commands, interpret expressions, or otherwise use the form of {accept input line; perform action based on the input; print the results; repeat}.
Real
DF file: Real.df
Documentation: MesaFloat60.bravo | Real.mesa | Ieee.mesa | see maintainer
Maintainer: CedarSupport^.pa
Real is the Cedar support for IEEE 32-bit floating point numbers.
ReleaseTool
DF file: ReleaseTool.df
Documentation: see maintainer
Maintainer: CedarSupport^.pa
The ReleaseTool is used to verify the completeness and consistency of releases. The UnreleaseTool is used to prepare the directory of the next release from the current release. CheckBasicLoadees is used to check for updates to members of Basic.Loadees.
Rollback
DF file: Rollback.df
Documentation: see maintainer
Maintainer: CedarSupport^.pa
RollbackImpl is the basic internal support for maing checkpoints and rolling the machine back to them.
Rope
DF file: Rope.df
Documentation: RopeDoc.tioga | see maintainer
Maintainer: Atkinson.pa
The Rope package, exports the familiar old interfaces Ascii, ConvertUnsafe, RefText, and Rope.
For Cedar6.0 the representation of Rope dropped the old PieceMap operation and added AppendChars. Most other changes simply fixed minor bugs or improved performance.
Rosary
DF file: Rosary.df
Documentation: RosaryDoc.tioga | see maintainer
Maintainer: Plass.pa
Rosary maintains immutable sequences of REFs. Rosary is used by Tioga to maintain character properties.
RPCRuntime
DF file: RPCRuntime.df
Documentation: see maintainer |
LupineRuntime.mesa, RPC.mesa, RPCLupine.mesa, RPCWatch.mesa
Maintainer: CedarSupport^.pa
Basic runtime support for Remote Procedure Call.
SafeStorage
DF file: SafeStorage.df
Documentation: SafeStorage.mesa, CountedVM.mesa | see maintainer
Maintainer: Atkinson.pa
Cedar runtime support for reclaimable reference-counted storage. The SafeStorage package exports the interfaces Atom, CountedVM, List, SafeStorage, SweepCollectableStorage, and UnsafeStorage. For Cedar 6.0 the medium-grain allocator has been retired, thereby eliminating a significant source of fragmentation.
Atom - contains procedures for creating atoms, and for storing and retrieving information on property lists. Property lists are lists of name value pairs that are usually associated with an atom, but can also be manipulated directly using procedures in this interface, e.g., the data field in a Viewer is usually a property list so that various clients can associate data with a viewer without getting in each others way.
List - contains various useful procedures for dealing with LIST OF REF ANY, e.g., Append, Member, NthTail, Union, Reverse, Sort, etc. For applications that traffic in LIST OF particular REF, e.g., LIST OF ATOM, it is necessary (but acceptable) to LOOPHOLE the list into a LIST OF REF ANY and then use a procedure in this interface. (For those procedures that return a LIST OF REF ANY value, it may be necessary to LOOPHOLE this value back into the LIST OF particular REF).
Scaled
DF file: Scaled.df
Documentation: Scaled.mesa
Maintainer: Plass.pa
Supports scaled fixed-point numbers.
Sequin
DF file: Sequin.df
Documentation: Sequin.mesa | see maintainer
Maintainer: CedarSupport^.pa
Sequin supports a full-duplex sequential stream of packets on the Ethernet. It is primarily used to support IFSFile (Leaf access to IFS). There are no functional changes since Cedar 4.4, although there is a greater use of SafeStorage facilities.
SimpleTerminal
DF file: SimpleTerminal.df
Documentation: SimpleTerminal.mesa
Maintainer: CedarSupport^.pa
SimpleTerminal provides a simple TTY-style screen, which is the basic terminal support during booting prior to Viewers.
STP
DF file: STP.df
Documentation: STP.mesa | see maintainer
Maintainer: CedarSupport^.pa
This is the Stream Transfer Protocol that underlies much of FS.
Tapes
DF file: Tapes.df
Documentation: see Maintainer
Maintainer: Diebert.pa
This package allows access to the network tapeserver in both record by record operations and stream operations. Documentation is in the interfaces.
Tentacles
DF file: Tentacles.df
Documentation: see maintainer
Maintainer: CedarSupport^.pa
Low-level support for teledebugging, boot file formats, and other tentacles into the external world.
Terminal
DF file: Terminal.df
Documentation: see maintainer
Maintainer: Wyatt.pa
Terminal provides a facility for multiplexing virtual terminals on a single physical terminal.
Tioga
DF file: Tioga.df
Documentation: TiogaDoc.tioga
Maintainer: TiogaImplementors^.pa
The standard Cedar text editor.
TiogaButtons
DF file: TiogaButtons.df
Documentation: TiogaButtons.mesa | see maintainer
Maintainer: Beach.pa
Provides a means for placing a lot of active text that responds to button clicks. Much better than the Buttons interface in Viewers for lots of buttons with fancy formatting.
TIP
DF file: TIP.df
Documentation: TIPDoc.tioga
Maintainer: TiogaImplementors^.pa
TIP is the middle-level keyboard and mouse event parser. TIP is the source of input events for Viewers and Tioga. The source of primitive events for TIP is Inscript.
TJaM
DF file: TJaM.df
Documentation: see maintainer
Maintainer: TiogaImplementors^.pa
TJaM, formerly included under Tioga.df, is now a separate package. It is used by Tioga's style machinery. TJaM is an obsolescent non-Cedar package; prospective clients should ask TiogaImplementors^ about the new Cedar JaM package.
TRope
DF file: TRope.df
Documentation: see maintainer
Maintainer: TiogaImplementors^.pa
TRope, formerly included under Tioga.df, is now a separate package. It exports the public interfaces RopeIO and RopeReader (also the more private interfaces RopeEdit, RopeFrom, and RopeEditingBLT).
UserCredentials
DF file: UserCredentials.df
Documentation: UserCredentials.mesa | see maintainer
Maintainer: CedarSupport^.pa
UserCredentials provides centralized management of the credentials of the user at the terminal.
UserProfile
DF file: UserProfile.df
Documentation: UserProfileDoc.tioga
Maintainer: CedarSupport^.pa
UserProfile provides centralized user option handling for the rest of Cedar.
VersionMap
DF file: VersionMap.df
Documentation: VersionMap.mesa, VersionMapDefaults.mesa | see maintainer
Maintainer: Atkinson.pa
VersionMap provides two fast maps: from version stamps to long names, and from short names to long names. This facility is used for debugging.
VersionMapBuilder
DF file: VersionMapBuilder.df
Documentation: see maintainer
Maintainer: Atkinson.pa
VersionMapBuilder provides facilities for building version maps from DF files.
ViewerIO
DF file: ViewerIO.df
Documentation: ViewerIO.mesa | see maintainer
Maintainer: Wyatt.pa
Formerly part of Tioga.df. Provides a means of creating streams to/from typescript viewers.
Viewers
DF file: Viewers.df
Documentation: ViewerDoc.tioga (obsolete) | see maintainer
Maintainer: TiogaImplementors^.pa
The Viewers Window Package is the arbiter of the user input and display hardware in the Cedar programming environment. It provides the illusion to the programmer that there is a private display, mouse and keyboard associated with each application, while allowing the user to simultaneously interact with many such applications.
The basic object manipulated by client programs and visible to the user is the viewer; a rectangular area with arbitrary contents which may be made visible on the user display. A viewer takes its name in that it allows the human user to view and interact with the data associated with a Cedar application. The underlying applications software has complete control over the displayed contents of a viewer and has available a rich user interface for user input. The screen position and size of a viewer may be modified by the user as well as under program control.
VM
DF file: VM.df
Documentation: VM.mesa, VMStatistics.mesa | see maintainer
Maintainer: CedarSupport^.pa
Cedar virtual memory support.
VTables
DF file: VTables.df
Documentation: VTables.mesa | see maintainer
Maintainer: Atkinson.pa
VTables is a package that provides a Viewer class for tabular organization of viewers. It supports rectangular organization with optional borders, automatic sizing, and addition, deletion, and swapping of rows and columns of viewers.
Watch
DF file: Watch.df
Documentation: WatchDoc.tioga
Maintainer: Atkinson.pa
This Tool runs in background and cheaply monitors various kinds of resource usage (storage allocation, CPU load, page fault rate, free VM pages, largest run of free VM pages, free MDS pages, etc.) The VM run is calculated twice per minute, but will be calculated immediately if you click the "Sample" button. Other information is sampled at a rate given after the "Interval" button. Left-clicking the "Interval" or "GC Interval" button doubles the parameter associated with the button, right-clicking halves the parameter.
WorldVM
DF file: WorldVM.df
Documentation: AMProcessBasic.mesa, WorldVM.mesa | see maintainer
Maintainer: CedarSupport^.pa
Provides low-level access to address spaces for local, world-swap, and remote debugging.