CLIM 2 on Symbolics Genera

Dynamic Windows relationship

Dynamic Windows and CLIM share a semantic presentation philosophy, a broadly similar graphics model, program/application frames, command processing, completion, and context-sensitive help. The manual nevertheless distinguishes their architectures:

The manual says Genera applications need not be converted merely because CLIM exists. Portability or use of CLIM's higher-level facilities are reasons to convert; TV-era programs often require redesign because their low-level event and window-flavor architecture has no mechanical CLIM analogue. The separate Dynamic Windows dossier documents the native Genera lineage.

Documented installation sequence

CLIM 2.0 was distributed with Genera 8.3. The release notes require a world without CLIM 1.0 or 1.1 already loaded; CLIM 2 cannot be overlaid on those releases. The documented sequence is:

1. restore CLIM, Genera-CLIM, and any desired CLX-CLIM, PostScript-CLIM, and CLIM-Demo systems from distribution media;
2. load CLIM first;
3. load Genera-CLIM for the native port;
4. optionally load the CLX, PostScript, and demo systems; and
5. save a new world if CLIM should survive reboot.

CLIM-Doc supplies the installed documentation family. The six release families therefore have distinct jobs:

Media versions are not one number

Two installed records describe different release moments:

• sys.sct/sct/system-info.lisp.~206~ lists all six VLM CLIM families at version 64.0. The adjacent 8.3 VBin declaration repeats that baseline.
• Each inspected CLIM-family patch system directory says :RELEASED 72 :LATEST 72.

This is not evidence that the binaries are simultaneously version 64 and 72. The system-info roster is a baseline/release inventory; the patch directories describe the later media patch lineage. The museum reports both and does not overwrite the older roster with the newest patch-directory number.

What the fresh world actually contains

The preserved Genera-8-5.vlod did not have CLIM loaded or registered. Two read-only Listener queries produced these results:

• scanning SCT::*ALL-SYSTEMS* for names containing CLIM returned NIL;
• (LIST (FIND-PACKAGE "CLIM") (MEMBER :CLIM *FEATURES*)) returned (NIL NIL).

The declaration itself pushes :CLIM, :CLIM-2, :CLIM-2.0, and :SILICA when loaded, so the absent package and features independently support the conclusion. No Load System CLIM attempt was made: the isolated museum session has no guest-visible host file service, and optional-system loading through SYS: would either block or test site configuration rather than CLIM behavior. A runnable CLIM frame therefore remains runtime-blocked, not inferred from media presence.

CLIM-UTILS: portability and mathematical substrate

The 23 compiled utility modules normalize Lisp, CLOS, conditions, streams, processes, queues, timers, protocols, transformations, regions, and designs across supported implementations. Declared groups are:

The declaration says CLIM follows the Gray stream proposal's split between ordinary stream entry points and generic stream methods. Conditional features decide whether CLIM supplies stream classes, trampoline functions, or vendor adapters. Genera uses its own stream adapter and existing stream functions.

CLIM-SILICA: sheets, ports, media, and gadgets

Silica has 23 compiled modules. Its first layer declares macros, classes, text styles, sheets, mirrors, events, ports, media, frame managers, graphics, and pixmaps. Its second layer—called Windshield/Dashboard in comments—implements portable layout and physical gadgets: boxes, tables, borders, scroll panes, buttons, sliders, and other standard sheets. Standard sheets and image support complete the declared set.

Silica terminology separates concerns:

CLIM-STANDALONE: the application-facing system

The standalone layer contains 60 compiled modules. All declared groups are included below; this is the core module inventory at a useful museum grain:

Genera, CLX, and PostScript ports

The main declaration also contains Allegro-only Xlib, Motif, and OpenLook toolkit systems. They are conditional and include explicitly ignored source paths; they are not Genera toolkit implementations. Genera instead uses CLIM's portable gadgets.

Presentation-based interaction

CLIM keeps application objects linked to their text or graphical display records. An input context asks for a presentation type. CLIM can then recognize eligible displayed objects, highlight them, translate them to another object or a command, or accept typed input through the same type. Views let one type have textual, dialog, menu, or gadget presentations. The type lattice is fixed at load time; type methods and translators specialize through CLOS-like inheritance.

This is semantic interaction rather than an active-region-only model. It also is not identical to a widget callback: a presentation may be any recorded application output, nested within other presentations and reusable in multiple contexts.

Output, spatial lookup, and redisplay

Output-record streams retain a hierarchy of recorded text, graphics, and designs. The declaration's coordinate-sorted set and R-tree modules reveal that visible record lookup is a spatial problem, not a linear repaint transcript. Formatted tables, graphs, text, and borders build output-record structure. Incremental redisplay then uses update records and application-supplied identities/state to decide which regions can be retained, moved, or repainted.

The release notes name fixes to clipping, overlapping records, tables, graph output, multiline highlighting, and design reconstruction. These are evidence that recording, hit testing, layout, and redisplay interact; a screenshot of final pixels cannot by itself establish the retained record structure.

Commands and application frames

DEFINE-APPLICATION-FRAME defines a CLOS frame with application state, panes, layouts, command tables, a top-level loop, and display functions. The ordinary programmatic path is MAKE-APPLICATION-FRAME followed by RUN-FRAME-TOP-LEVEL; FIND-APPLICATION-FRAME can combine creation, activation, process choice, and port/frame-manager selection.

On Genera, DEFINE-GENERA-APPLICATION registers a frame with Select Activity and can assign a Select key, pretty name, geometry, and size. It is a Genera-only integration form, not part of a portable application's core definition. CLIM-created application frames appear in Genera's System Menu under their application names.

Standard pane families include application, interactor, command-menu, pointer documentation, accepting-values, title/status, layout, scrolling, and portable gadgets. Applications may use textual or gadget views. The release notes emphasize that Genera has portable CLIM gadgets rather than a Motif binding.

Sixteen named feature additions

Nineteen named fix or enhancement families

The release notes separately identify 19 changes: string accept/present conversion; sensitive inferiors; multiline highlighting; completion over union types; parameterized identity translators; clipping regions; input-buffer clear-and-click; input-editor typeout placement; dialog Help windows; automatic argument delimiters; faster text and diacritics; partially improved coordinate-sorted sets; incremental redisplay for tables, graphs, and overlap; faster filling output; button-up handling in pointer tracking; repeated-border alignment; design reconstruction from records; Genera Suspend/Meta-Suspend behavior; and PostScript font metrics. “Partially improved” is retained for coordinate-sorted sets because the release notes explicitly do not claim a complete fix.

Activation, completion, and command entry

There is no global delimiter gesture for all types. Recursive ACCEPT methods choose their own delimiters; Space is the command processor's default. Numeric arguments to editor commands use digits or minus with Control, Meta, Super, or Hyper.

All 36 built-in input-editor commands on Genera

Dialogs and menus

The absence of special menu commands does not mean menus are pointer-only in every application: command tables and accelerators can still bind application commands. It means CLIM 2's default menu surface adds no separate universal key set.

Debugger placement

The Genera Debugger cannot render itself inside a full-screen CLIM window. An error there produces a notification; the developer selects a Listener to use the Debugger, then reselects the application—through its window, activity, System Menu entry, or Select key—after arranging a suitable restart. This is a port/UI boundary, not a claim that CLIM has its own independent debugger.

Color

On a two-headed Genera system, an application explicitly finds the color screen, creates a CLIM port for that server path, and supplies the port when constructing the frame. On native-color Ivory platforms, the port detects color support without that special selection. The current museum VLM display is monochrome, so neither path was runtime-verified here.

CLX and PostScript

CLX-CLIM is present but the manual calls it an unsupported sample port for people studying how to implement a port. That warning prevents “included” from being rewritten as “supported production X client.” PostScript-CLIM is an output port with its own medium and LaserWriter metrics; release notes report corrected font metrics, but no configured printer or output comparison was exercised.

Findings established across layers

• CLIM is optional and layered; the portable core, native port, output ports, documentation, and demos are separate systems.
• The native integration is through a Genera port and activity registration, not by renaming Dynamic Windows.
• Presentations, command tables, output records, formatted output, incremental redisplay, application frames, panes, and gadgets form one connected architecture.
• The saved museum world lacks the package/features that the declaration installs, so media presence does not establish live availability.

Declaration/media findings the manual does not make obvious

• The 106 core compiled modules divide exactly into 23 utilities, 23 Silica modules, and 60 standalone modules; the three ports add 19 more.
• The inspected media exposes declaration source but only compiled implementation bodies. This prevents a function-body audit even though the module architecture is unusually well preserved.
• The declaration conditionally extends CLOS presentation-type method inheritance on Genera and conditionally adapts vendor condition and stream facilities.
• Allegro-only Motif/OpenLook/Xlib declarations coexist in the portable declaration but are not Genera facilities; some are explicitly ignored source paths.
• The patch directories say released 72 while the VLM system-info roster says 64. These records describe different inventory/patch layers and must not be flattened.
• Recovered Help contains 34 CLIM SAB files, 1,297 records, and 2,545,599 source bytes across applications, geometry, color, commands, drawing, graphs/tables, redisplay, panes, presentations, regions, Silica, streams, toolkit use, tutorials, user guide, dictionary, glossary, release notes, and hardcopy. Those are local documentation-presence counts, not permission to publish the decoded text.

Runtime record and screenshot decision

The raw status screens are retained only as local provenance: 0010-clim-system-status-runtime.png is 11,748 bytes with PNG SHA-256 50cfae39733ca7815ca0dd150aa1d659987ada8a2961f593610fe43dcab97b0c and normalized-pixel SHA-256 82dca042cd4c94cc0560999ff96836a0aa6c571898387a68c73e6d6f6ef0d6e1; 0011-clim-package-feature-status.png is 11,852 bytes with PNG SHA-256 cc64888a59e7850ae526ca08cc17ba050d4d8832eb1b9df8d2a9a724e5abbccc and normalized-pixel SHA-256 8de9dc9ccbb2da887f29f57cdeb265aac1a2517f29942d9efa6a3b85af4056bc. Neither image depicts CLIM, so neither passed the museum's usefulness threshold for publication.

Contemporary public manuals

Licensed declarations and inventories

Compiled module census

The counts select versioned .vbin files directly within each named directory. They do not count declarations, patch metadata, documentation, tutorial code, demos, or tests as implementation modules.