In Oberon, the text on the screen wasn't just static data; it was a live map of objects. Wirth implemented a concept called "any text is a command line." You could define a word as a specific object type—say, a graphic, a table, or a code module—and the Tiler would render it accordingly right there in the text stream.
Furthermore, the concept of the "object" as a tile-able entity foreshadowed modern document-oriented interfaces like Google Chrome’s tabbed browsing or Visual Studio Code’s split-editor groups. In each case, the goal is to treat content (not windows) as the primary unit of interaction and to provide a predictable, space-efficient layout. Oberon Object Tiler
: This is the "Bible" of Oberon. It provides a complete description of the system's inner workings, including how the display and tiling mechanisms (viewers) were implemented with extreme efficiency. Oberon: Design and Language Evolution In Oberon, the text on the screen wasn't
Niklaus Wirth and Jürg Gutknecht built Oberon for productivity. They observed that traditional overlapping window systems waste cognitive energy. Every time a user brings a window to the front, they lose spatial context. In each case, the goal is to treat