Oberon System Interface vs Terminal UI
オベロン・システムの画面 / ターミナルUI
Oberon System Interface comes from Platform Screen Languages and Terminal UI from UI Expression. One is layout and the other style. They are reached for with some of the same intent, which is where they get confused.
Oberon System Interface
The screen of the system Niklaus Wirth and Jürg Gutknecht built at ETH between 1986 and 1989. Windows never overlap: the display is split into vertical tracks and each track is tiled top to bottom. Any text anywhere on the screen can be run as a command if it reads M.P and you click it with the middle button, so the system needs no menu widget at all.
Terminal UI
The terminal look: monospaced phosphor characters on black. The VT100's green afterglow became the primal image of the computer's face, repeated from hacker cinema to modern CLI tools.
| Oberon System Interface | Terminal UI | |
|---|---|---|
| Era | 1988– | 1970s– |
| Family | Platform Screen Languages | UI Expression |
| Kind | Layout | Style |
| Cues | Nothing overlaps: the display is cut into vertical tracks first, then tiled top to bottom inside each track / A narrow track on the right holds a log above and a text of commands below, with the wide working track on the left / A one line title bar across the top of every viewer, carrying the document name and commands such as System.Close as plain text / One bit per pixel, black on white, with borders drawn as single lines and no shadow, rounding or grey | Single phosphor color on black / The monospace grid / A blinking cursor / Scanlines and glow |
| Best used for | Designing a workspace that gives up overlapping windows, where placement is decided by only two moves: which track, and where in that track · Giving a product a command list the user can rewrite, held as an ordinary editable text instead of a dedicated menu component | Developer tools packing state and next steps into one monospaced screen · Staging technical hardness or secrecy as the look of an interface |
| Type | Set commands in the same face and size as body text. Name them M.P and spell them out as words, Copy and Rename rather than cp and rn. | One monospaced face where emphasis comes from weight and inversion alone |
| Composition | Cut the display into vertical tracks and divide each track horizontally. Never overlap. Keep a narrow right hand track for the log and the command text and leave the left wide. Give every viewer a one line title bar. | Everything on the column and row grid, blocks separated by blank lines |
| Material | One bit, black on white. Single pixel rules, no shadow, no rounded corners, no greys and no colour. Mark the insertion point with a hook. | One phosphor hue on black with scanlines and bloom added sparingly |
| Caution | Copying the tiling without the rule that any text on screen is executable forces the menu bar and the buttons back in, and all that is left is a cramped layout. | Heavy scanlines and flicker cost legibility and the atmosphere ends up beating the speed that made the tool worth using. |