Menu bar

A menu bar is a region where computer menus are housed. Its purpose is to house window- or application-specific menus which provide access to such functions as opening files, interacting with an application, or help. Menu bars are typically present in graphical user interfaces with windows.

Menu bar from Mozilla Firefox.

Implementations

Through the evolution of graphical user interfaces, the menu bar has been implemented in different ways by different operating systems.

Macintosh

Menu bar from Mac OS X v10.5.

In the Macintosh operating system, the menu bar is a horizontal "bar" anchored to the top of the screen. On the left side, it contains the Apple menu and the currently focused application's menus (e.g File, Edit, View, Window, Help). On the right side, it contains menu extras (for example the system clock, volume control, and the Fast user switching menu if enabled) and the Spotlight icon. All of these menu extras (excluding Spotlight) can be moved horizontally by command-clicking and dragging left or right. If an icon is dragged and dropped vertically it will disappear with a puff of smoke, much like the icons in the dock.

There is only one menu bar, so the application menus displayed are those of the application that is currently focused. Therefore, for example, if the System Preferences application is focused, its menus are in the menu bar, and if the user clicks on the Desktop which is a part of the Finder application, the menu bar will then display the Finder menus.

Early Apple experiments in GUI design initially used multiple menu bars anchored to the tops of windows, but this was quickly dropped in favor of the current arrangement. [1] The idea of separate menus in each application was later implemented in Microsoft Windows. The menu bar first appeared in the Apple Lisa operating system in 1983, and has been a feature of all versions of the Macintosh operating system since the first Macintosh was released in 1984. It is still present in Mac OS X.

Microsoft Windows

The menu bar in Microsoft Windows is usually anchored to the top of a window under the title bar; therefore, there can be many menu bars on screen at one time. Menus in the menu bar can be accessed through shortcuts involving the Alt key and the mnemonic letter that appears underlined in the menu title. Additionally, pressing Alt or F10 brings the focus on the first menu of the menu bar.

Linux and UNIX

Screenshot of KDE 3.5 showing multiple menu bars

Screenshot of KDE 3.5 configured with a single menu bar

KDE allows users to turn Macintosh-style and Windows-style menu bars on and off. It is possible to have both types in use at the same time.

GNOME uses a menu bar at the top of the screen, but this menu bar only contains Applications and System menus and status information (such as the time of day); individual programs have their own menu bars as well. However, it is possible to change this behavior for some applications, see [2].

Other window managers and desktop environments use a similar scheme, where programs have their own menus, but clicking one or more of the mouse buttons on the root window brings up a menu containing, for example, commands to launch various applications or to log out.

Window manager menus in Linux are typically configurable either by editing text files, by using a desktop-environment-specific Control Panel applet, or both.

Window Managers That Provide A Menubar

• amiwm (Temporary menubar provides a box to enter commands, programs not listed, no start button, not a taskbar)
• cwm
• fluxbox (Provides a combined taskbar showing running applications)
• fvwm95 (Provides a start button and combined taskbar showing running applications)
• icewm (Provides a start button and combined taskbar showing running applications)
• jwm (Provides a start button and combined taskbar showing running applications)
• qvwm (Provides a start button and combined taskbar showing running applications)
• whim
• windowlab
• xpwm (Provides a start button and combined taskbar showing running applications)

Commodore Amiga

The Amiga used a menu-bar style similar to the Macintosh, with the exception that the machine's custom graphics chips allowed each program to have its own "screen", with its own resolution and colour settings, which could be dragged down to reveal the screens of other programs. The title/menu bar would typically sit at the top of the screen, and could be accessed by pressing the right mouse button, revealing the names of the various menus. When the right menu button was not pressed down, the menu/title bar would typically display the name of the program which owned the screen, and some other information such as the amount of memory used.

The Workbench screen title bar would typically display the internal Kickstart and Workbench version, the total amount of chip and fast memory, and the amount of free Chip RAM and Fast RAM. An unusual feature of the Amiga menu system was that the Workbench screen would display a "Workbench" menu instead of a "File" or "Apple" menu, whilst conforming applications would display "Project" and "Tools" menus (projects and tools being, respectively, the Amiga terms for what in other systems are called files or documents, and programs or applications).

Keyboard shortcuts could be accessed by pressing the left-hand "left Amiga" key along with a normal alphanumeric key. (Some early keyboards had a Commodore key to the left of the spacebar instead of a "left-Amiga" key.) The filled-in and hollowed-out designs, respectively, of the left-and-right Amiga (or Commodore and Amiga) keys were inspired by the similar closed-Apple and open-Apple keys of Macintosh and Apple II keyboards.

NeXTstep

The NeXTstep OS for the NeXT machines would display a "menu list", by default at the top left of the screen. Clicking on the entries in the menu list would display submenus of the commands in the menu. The contents of the menu change depending on whether the user is "in" the Workspace Manager or an application. The menus and the sub-menus can easily be torn off.

Power users would often switch off the always-on menu, leaving it to be displayed at the mouse pointer's location when the right mouse button was pressed. The same implementation is used by GNUstep and conforming apps, though applications written for the host operating system or another toolkit will use the menu scheme appropriate to that OS or toolkit.

Atari TOS

The TOS operating system for the Atari ST would display menu bars at the top of the screen like Mac OS.

RISC OS

In RISC OS, clicking the middle button displays a menu list at the location of the mouse pointer. The RISC OS implementation of menus is similar to the context menus of other systems, except that menus will not close if the right mouse button is used to select a menu entry. This allows the user to implement or try out several settings before closing the menu.

Ease of use

In both Microsoft Windows and Apple Macintosh operating systems, other similar desktop environments and some applications, common functions are assigned keyboard shortcuts (for example Control-C or Command-C copies the current selection).

Microsoft style menu bars are physically located in the same window as the content they are associated with. However, Bruce Tognazzini, former employee of Apple Inc. and human computer interaction professional, claims^[1] that the Mac OS's menu bars can be accessed up to five times faster due to Fitts's law: because the menu bar lies on a screen edge, it effectively has an infinite height — Mac users can just "throw" their mouse pointers toward the top of the screen with the assurance that it will never overshoot the menu bar and disappear (this requires that the cursor move purely vertically, however, as it will continue to slide horizontally when it hits the screen edge). After Apple discovered this, they claimed copyright and patent rights on the Apple menu bar.^[2]

This assumes that the desired menu is currently enabled, however. If another application has "focus", the menu will belong to that application instead, requiring the user to check and see which menu is active before "throwing" the mouse, and often perform an extra step of focusing the desired application before using the menu, which is completely separate from the application it controls. The effectiveness of this technique is also reduced on larger screens or with low mouse acceleration curves, especially due to the time required to travel back to a target in the window after using the menu.^[3] When using dual monitors, the menu can be on an entirely different screen from the application it is controlling, requiring much more mouse movement.^[4][5]

References