{"id":"oberon-system-ui","no":536,"name":"Oberon System Interface","ja":"オベロン・システムの画面","era":"1988–","family":"プラットフォームの画面言語","kind":"レイアウト","collection":"Dictionary expansion 26","addedAt":"2026-08-19","source":{"title":"ETH Zürich / Niklaus Wirth — Project Oberon (New Edition 2013)","url":"https://people.inf.ethz.ch/wirth/ProjectOberon/index.html"},"reference":{"status":"verified","pageUrl":"https://people.inf.ethz.ch/wirth/ProjectOberon/index.html","credit":"ETH Zürich / Niklaus Wirth — Project Oberon (New Edition 2013)","gallery":[{"imageUrl":"https://commons.wikimedia.org/wiki/Special:FilePath/Oberon0UnderQEMU.png?width=640","pageUrl":"https://commons.wikimedia.org/wiki/File:Oberon0UnderQEMU.png","credit":"Oberon-0の画面、タグ行と敷き詰めた面 — Wikimedia Commons / CC BY-SA 4.0"},{"imageUrl":"https://commons.wikimedia.org/wiki/Special:FilePath/OberonV4.on.iMacM1.png?width=640","pageUrl":"https://commons.wikimedia.org/wiki/File:OberonV4.on.iMacM1.png","credit":"Oberon V4の画面、二列のタイリング — Wikimedia Commons / CC BY-SA 4.0"},{"imageUrl":"https://commons.wikimedia.org/wiki/Special:FilePath/TatungTWN5213Oberon.png?width=640","pageUrl":"https://commons.wikimedia.org/wiki/File:TatungTWN5213Oberon.png","credit":"PC Native Oberonを表示したタブレット — Wikimedia Commons / CC BY-SA 4.0"}]},"essence":"ヴィルトとグートクネヒトがETHで1986年から89年に作ったシステムの画面。窓を重ねず、画面を縦の帯に割ってその中を上下に敷き詰める。画面上のどの文字も M.P の形なら中ボタンで実行できるため、メニューという専用の部品を持たない。","cues":["窓が重ならない。画面がまず縦の帯に割られ、帯の中で上下に敷き詰められる","右に細い帯があり、上にログ、下にコマンドを並べたテキストが置かれる。左の広い帯が作業用","各ビューアの上端に一行分の細い枠があり、文書名と System.Close などのコマンドが文字として並ぶ","1ピクセル1ビットの白黒。枠は細い直線だけで、影も丸みも階調もない"],"intents":["技術","静けさ","反骨"],"works":["窓の重なりを捨てた作業画面を設計するとき、縦の帯と帯内の分割という二段階だけで配置を決める","コマンド一覧を専用のUI部品ではなく、利用者が自分で書き換えられるテキストとして持たせたいとき"],"recipe":{"type":"コマンドも本文と同じ字面で置く。名前は M.P の形にし、cp のような略語ではなく意味の通る語を綴る。","layout":"画面を縦の帯に分け、帯の中を上下に区切る。重ねない。右に細い帯を取ってログとコマンド用テキストを置き、左を広く空ける。ビューアの上端には一行の題名枠を付ける。","material":"白地に黒の1ビット。線は1ピクセル幅の直線で、影も角丸も階調も色も使わない。挿入位置は鉤形の印で示す。"},"avoid":"重ねない配置だけを真似ても、画面上のどの文字もコマンドになるという規則がなければ、結局メニューバーとボタンを足すことになり、窮屈なだけの画面になる。","colors":["#FFFFFF","#000000","#808080"],"motif":"graphic","pair":["motif","terminal-ui"],"study":["Project Oberon の第4章で、自由なタイリングと階層的タイリングがなぜ比較され、どちらが選ばれたかを読む","System.Tool の中身を見て、コマンド一覧がただのテキストとして編集できることの意味を確かめる","3ボタンの割り当て、左でカーソル位置、中でコマンド、右で選択という規則がどこまで一貫しているかを追う"],"en":{"essence":"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.","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"],"works":["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"],"recipe":{"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.","layout":"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.","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."},"avoid":"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.","study":["chapter 4 of Project Oberon, on why free tiling and hierarchical tiling are compared and which was chosen","the contents of System.Tool, and what it means that the command list can be edited as plain text","how consistently the three button rules hold, left for the cursor position, middle for commands, right for selection"]}}