{"id":"acme-interface","no":535,"name":"Acme","ja":"アクメ・インターフェース","era":"1994–","family":"プラットフォームの画面言語","kind":"スタイル","collection":"Dictionary expansion 26","addedAt":"2026-08-19","source":{"title":"Bell Labs / Plan 9 — Acme: A User Interface for Programmers (Rob Pike)","url":"https://9p.io/sys/doc/acme/acme.html"},"reference":{"status":"verified","pageUrl":"https://9p.io/sys/doc/acme/acme.html","credit":"Bell Labs / Plan 9 — Acme: A User Interface for Programmers (Rob Pike)","gallery":[{"imageUrl":"https://commons.wikimedia.org/wiki/Special:FilePath/Plan%209%20from%20Bell%20Labs%20(with%20acme).png?width=640","pageUrl":"https://commons.wikimedia.org/wiki/File:Plan%209%20from%20Bell%20Labs%20(with%20acme).png","credit":"Plan 9 from Bell Labsのacme画面 — Wikimedia Commons / CC BY-SA 4.0"}]},"essence":"Rob Pike が1994年の論文で示した、窓とシェルと編集機を一つにした画面。メニューもアイコンも持たず、画面上のどの文字列も中ボタンで実行でき、右ボタンで開ける。窓は縦の列に積まれ、一行のタグと本文という二段だけでできている。","cues":["窓が縦の列に積まれ、各窓は一行のタグと本文の二段でできている","スクロール帯が本文の左端にあり、右端には何も置かれない","中ボタンで文字列をなぞると、押している間だけその文字列に下線が引かれる","本文は淡い黄色、タグは淡い水色で、押すためのボタンもアイコンも一つもない"],"intents":["技術","静けさ","反骨"],"works":["道具を足すのをやめ、文字を打てる場所すべてを命令の置き場にした作業画面をつくるとき","使う人が自分でタグに命令を書き足していく、部品の少ない開発用の画面を組むとき"],"recipe":{"type":"一書体で通し、大きさも一段だけ。太字も色文字も使わず、下線と選択の反転だけで状態を示す。","layout":"画面を縦の列に割り、列の中に窓を積む。各窓は一行のタグと本文の二段。余白は取らず、細い枠線一本で隣と分ける。","material":"地色は二種だけ。本文に淡い黄色、タグに淡い水色を敷き、文字は黒にする。実行の下線には暗い赤、参照の下線には暗い緑を当て、変更のあった窓はタグ左端の小さな四角の中心を塗る。"},"avoid":"見た目だけ真似てタグを固定のメニューにすると、どの文字列も命令になるという中身が消える。","colors":["#FFFFEA","#EAFFFF","#AA0000"],"motif":"graphic","pair":["terminal-ui","motif"],"study":["Rob Pike の論文が置く『window system と shell と editor の hybrid』という定義","タグの縦棒より右が自由記入の余白になっていて、書いた命令がそのまま残る仕組み","同じ論文が比較している Oberon と Cedar から、受け継いだ点と外した点"],"en":{"essence":"Acme is the interface Rob Pike described in a 1994 paper, a hybrid of window system, shell and editor. It has no icons and no pop-up or pull-down menus; any string anywhere on screen can be executed with the middle button or opened with the right one. Windows are stacked in columns, and each is only a one line tag above a body.","cues":["Windows are stacked in columns, and each window is just a one line tag above a body","The scroll bar sits at the left edge of the body, and nothing sits at the right","Sweeping a string with the middle button underlines it only while the button is held","The body is pale yellow and the tag pale blue, and there is not one button or icon to click"],"works":["When a working screen should stop gaining widgets and let every place you can type hold a command","When a development environment is meant to be extended by users typing commands into the tag themselves"],"recipe":{"type":"One typeface, one size. No bold and no coloured text; state is shown by an underline and by inverted selection only.","layout":"Split the screen into columns and stack windows inside them. Each window is a one line tag above a body. Take no margin, and separate neighbours with a single thin rule.","material":"Two ground colours only: pale yellow for the body, pale blue for the tag, black for the text. Underline execution in dark red and reference in dark green, and fill the centre of the small square at the left of the tag when the file has been modified."},"avoid":"Copy the look and turn the tag into a fixed menu, and you lose the actual mechanism, which is that any string at all can be a command.","study":["the definition Rob Pike's paper sets down, a hybrid of window system, shell and editor","the mechanism whereby everything to the right of the vertical bar in the tag is free scratch space, so a command written there stays put","what was carried over and what was left out from Oberon and Cedar, which the same paper compares"]}}