Widescreen laptops are dumb
&quot;As if all that wasn’t enough, there’s also the matter of tabs. Tabs are a couple of decades old now, and, like much of the rest of the desktop and web environment, they were initially thought up in an age where the predominant computer displays were close to square with a 4:3 aspect ratio.&quot;<p>Tabs are at least three decades old now, and they weren&#x27;t originally restricted to just one edge of the window:<p>&gt;Tab (GUI):<p><a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Tab_(GUI)" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Tab_(GUI)</a><p>&gt;The WordVision DOS word processor for the IBM PC in 1982 was perhaps the first commercially available product with a tabbed interface. PC Magazine in 1994 wrote that it &quot;has served as a free R&amp;D department for the software business—its bones picked over for a decade by programmers looking for so-called new ideas&quot;. The NeWS version of UniPress&#x27;s Gosling Emacs text editor was another early product, with multiple tabbed windows in 1988. It was used to develop an authoring tool for the Ben Shneiderman&#x27;s HyperTIES browser (the NeWS workstation version of The Interactive Encyclopedia System), in 1988. HyperTIES also supported pie menus for managing windows and browsing hypermedia documents with PostScript applets. Don Hopkins developed and released several versions of tabbed window frames for the NeWS window system as free software, which the window manager applied to all NeWS applications, and enabled users to drag the tabs around to any edge of the window.<p>Notice the layout of the overlapping Emacs windows with tabs sticking out of their right edge: since text is much wider than it is tall, you can stack up a lot more tabbed windows with tabs on their left or right side, and still read their labels.<p>&gt;HCIL Demo - HyperTIES Authoring with UniPress Emacs on NeWS:<p><a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=hhmU2B79EDU" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=hhmU2B79EDU</a><p>&gt;Demo of UniPress Emacs based HyperTIES authoring tool, by Don Hopkins, at the University of Maryland Human Computer Interaction Lab.<p>Notice how you can drag the tabs of these NeWS windows to any edge or proportion of the height or width, and use the tab as a proxy for the window by popping up a window management pie menu on it, even if the rest of the window is covered:<p>&gt;NeWS Tab Window Demo:<p><a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=tMcmQk-q0k4" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=tMcmQk-q0k4</a><p>&gt;Demo of the Pie Menu Tab Window Manager for The NeWS Toolkit 2.0. Developed and demonstrated by Don Hopkins.<p>Notice how the tabbed windows can be stuck on the visual PostScript stack like a short order chef&#x27;s &quot;spike&quot;. The tabs enable &quot;direct stack manipulation&quot;: and they are constrained (by &quot;snap dragging&quot;) to slide up and down on the stack (rearranging the order of the items on the PostScript stack), and can be pulled far enough away that they &quot;pop&quot; off the stack, or dragged back onto the stack so they snap into place, and you can directly drop them into any depth of the stack.<p>&gt;PSIBER Space Deck Demo:<p><a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=iuC_DDgQmsM" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=iuC_DDgQmsM</a><p>&gt;Demo of the NeWS PSIBER Space Deck. Research performed under the direction of Mark Weiser and Ben Shneiderman. Developed and documented thanks to the support of John Gilmore and Julia Menapace. Developed and demonstrated by Don Hopkins.
Described in &quot;The Shape of PSIBER Space: PostScript Interactive Bug Eradication Routines&quot;.<p>&gt;The Shape of PSIBER Space - October 1989.
PostScript Interactive Bug Eradication Routines.<p><a href="http:&#x2F;&#x2F;www.donhopkins.com&#x2F;drupal&#x2F;node&#x2F;97" rel="nofollow">http:&#x2F;&#x2F;www.donhopkins.com&#x2F;drupal&#x2F;node&#x2F;97</a><p>&gt;There is a text window onto a NeWS process, a PostScript interpreter with which you can interact (as with an &quot;executive&quot;). PostScript is a stack based language, so the window has a spike sticking up out of it, representing the process&#x27;s operand stack. Objects on the process&#x27;s stack are displayed in windows with their tabs pinned on the spike. (See figure 1) You can feed PostScript expressions to the interpreter by typing them with the keyboard, or pointing and clicking at them with the mouse, and the stack display will be dynamically updated to show the results.<p>&gt;Objects on the PSIBER Space Deck appear in overlapping windows, with labeled tabs sticking out of them. Each object has a label, denoting its type and value, i.e. &quot;integer 42&quot;. Each window tab shows the type of the object directly contained in the window. Objects nested within other objects have their type displayed to the left of their value. The labels of executable objects are displayed in italics. [...]<p>&gt;Tab Windows<p>&gt;The objects on the deck are displayed in windows with labeled tabs sticking out of them, showing the data type of the object. You can move an object around by grabbing its tab with the mouse and dragging it. You can perform direct stack manipulation, pushing it onto stack by dragging its tab onto the spike, and changing its place on the stack by dragging it up and down the spike. It implements a mutant form of &quot;Snap-dragging&quot;, that constrains non-vertical movement when an object is snapped onto the stack, but allows you to pop it off by pulling it far enough away or lifting it off the top. [Bier, Snap-dragging] The menu that pops up over the tab lets you do things to the whole window, like changing view characteristics, moving the tab around, repainting or recomputing the layout, and printing the view.<p>&gt;Designing to Facilitate Browsing: A Look Back at the Hyperties Workstation Browser.
By Ben Shneiderman, Catherine Plaisant, Rodrigo Botafogo, Don Hopkins, William Weiland.<p><a href="http:&#x2F;&#x2F;www.donhopkins.com&#x2F;drupal&#x2F;node&#x2F;102" rel="nofollow">http:&#x2F;&#x2F;www.donhopkins.com&#x2F;drupal&#x2F;node&#x2F;102</a><p>&gt;Since storyboards are text files, they can be created and edited in any text editor as well as be manipulated by UNIX facilities (spelling checkers, sort, grep, etc...). On our SUN version Unipress Emacs provides a multiple windows, menus and programming environment to author a database. Graphics tools are launched from Emacs to create or edit the graphic components and target tools are available to mark the shape of each selectable graphic element. The authoring tool checks the links and verifies the syntax of the article markup. It also allows the author to preview the database by easily following links from Emacs buffer to buffer. Author and browser can also be run concurrently for final editing. [...]<p>&gt;The more recent NeWS version of Hyperties on the SUN workstation uses two large windows that partition the screen vertically. Each window can have links and users can decide whether to put the destination article on top of the current window or on the other window. The pie menus made it rapid and easy to permit such a selection. When users click on a selectable target a pie menu appears (Figure 1) and allows users to specify in which window the destination article should be displayed (practically users merely click then move the mouse in direction of the desire window) . This strategy is easy to explain to visitors and satisfying to use. An early pilot test with four subjects was run, but the appeal of this strategy is very strong and we have not conducted more rigorous usability tests.<p>&gt;In the author tool, we employ a more elaborate window strategy to manage the 15-25 articles that an author may want to keep close at hand. We assume that authors on the SUN&#x2F;Hyperties will be quite knowledgeable in UNIX and Emacs and therefore would be eager to have a richer set of window management features, even if the perceptual, cognitive, and motor load were greater. Tab windows have their title bars extending to the right of the window, instead of at the top. When even 15 or 20 windows are open, the tabs may still all be visible for reference or selection, even thought the contents of the windows are obscured. This is a convenient strategy for many authoring tasks, and it may be effective in other applications as well.<p><a href="https:&#x2F;&#x2F;upload.wikimedia.org&#x2F;wikipedia&#x2F;en&#x2F;2&#x2F;29&#x2F;HyperTIESAuthoring.jpg" rel="nofollow">https:&#x2F;&#x2F;upload.wikimedia.org&#x2F;wikipedia&#x2F;en&#x2F;2&#x2F;29&#x2F;HyperTIESAuth...</a><p>Unfortunately most of today&#x27;s &quot;cargo cult&quot; imitative user interface designs have all &quot;standardized&quot; on the idea that the menu bars all belong at the top of the screen and nowhere else, menus items should layout vertically downward and no other directions, tabs should be rigidly attacked to the top edge and no other edge, and the user can&#x27;t move them around. But there&#x27;s no reason it has to be that way.