Are menus starting to disappear from the Linux desktop? A survey of the alternatives suggests that, at the very least, menus seem to be evolving out of recognition in response to modern trends, particularly the effort to make workstation and laptop desktops more like mobile interfaces. Ask usability experts, and the unexamined assumption is that the classic menu needs improvement -- although whether users feel that way seems less clear.
Ten years ago, desktop menus were straightforward. They listed most of the desktop applications, with sub-menus spilling across the desktop to help organize them. The most extreme case is the famous -- or infamous -- Debian menu, which descends four or five sub-levels, but contains every application installed on the system, if only you had the patience to keep searching. The Debian menu remains popular with some users today, including me.
So, for that matter, does the classical menu in general. Users of Xfce, LXDE, KDE 3 and other lesser-used free desktops continue to use the classical menu with few or no complaints. However, increasingly, on both free and proprietary desktops, the movement is away from the classical menu, although none of the existing alternatives is likely to satisfy anyone.
In some ways, the change was inevitable. Where hard drives once held dozens of applications, now they hold hundreds. Even on a workstation monitor, sub-menus can easily fill most of the screen. Alternatively, if you try to restrict the menu to two or three levels, which is the general trend, the height of the open menu frequently exceeds the height of the screen, even on workstations.
Nor is the situation helped by the fact that desktop designers are now putting more into the menu than ten years ago. Now, in addition to applications, menus are likely to include lists of favorite applications, locations, and files. Whether these extras serve any purpose varies with the user, but, since they are included by default, they add to the crowding on the menu for everyone. So far as I can tell, this crowding seems to have been born partly out of a wish to get away from icons or launchers on the desktop, even though both are popular with large numbers of users.
Along with these increased demands comes the assumption among usability experts that users -- especially new ones -- should not be overwhelmed by all the available choices, as they were in the past. Instead, only a selection of applications likely to interest new users would be included in the menu. The result was more elegant, less cluttered menus, but at the cost of concealing some applications so successfully that some users would probably never find them.
All these problems are magnified several times over by the smaller screens of netbooks and other mobile devices. Menus do, of course, exist on mobile devices, but often require complete changes of screen, as well as alternatives like scroll wheels to speed navigation. Instead, the mobile trend seems to be towards different forms of launchers, which can be described as a compromise between menus and desktop icons. Now, in new, mobile-inspired interfaces like Ubuntu's Unity or the upcoming GNOME 3.0, launchers rather than menus are being offered as the main navigation tool.
Some of the first attempts to improve the menu were merely organizational -- efforts to standardize or reduce the number of top level menus. GNOME in particular worked hard on this effort, with KDE not showing a similar concern until the fourth series of releases began. In addition, GNOME moved away from the single menu to a series of three: Applications, Places, Menu.
The trouble was, these organizational standards have never been consistent across distributions. Since menus are relatively easy to edit, distributions would arrange applications or functions as they saw fit. Although at first users switching between distros might think they know where to find their favorite applications, in practice, they usually have to do some searching.
Mercifully, no free desktop (so far as I am aware), ever attempted to emulate the so-called personalized menus in Windows that changed with your use and only showed the most frequently used menu items. The drawback to these personalized menus was the assumption in their design that most users only clicked regularly on a few items; if you wanted anything unusual, they required an extra click and a few seconds before you could seen a complete list of choices.
Instead, the free desktop has explored other alternatives in recent years. In KDE 4.0, KDE introduced Kickoff, which seems inspired by innovations introduced in Windows Vista without being entirely an imitation. Kickoff's main difference from the classical menu is to confine the display to a single window showing one level at a time. This structure makes Kickoff more suitable for smaller screens, but requires users to click back to a higher level before they can see, much less switch to another sub-menu.
To satisfy users, KDE continues to include the classical menu as an alternative to the default Kickoff. Moreover, KDE also includes a third menu choice called Lancelot among its desktop and panel widgets. Like Kickoff, Lancelot is confined to a single window on the desktop, but, unlike Kickoff, Lancelot also shows more than one menu level at once. This innovation makes navigation easier, but has the drawback of being cramped if more than three levels are visible at once; resizing the Lancelot window is possible, but requires some fiddling, even if the desktop widgets are unlocked.
More recently, designers have started exploring mobile-inspired desktops that abandon or minimize the classic menu altogether.
The first of these next-generation desktops to be released was KDE's Plasma Netbook. It moves the applications menu and the taskbar right on to the desktop, a solution that is legible and highly usable even on a small screen like those found on mobile devices. However, Plasma Netbook is no better at preserving screen space for applications than the classical menu.
One of the ways around the issues of security and control that make some businesses wary of cloud computing is to build a private cloud -- one that remains within the corporate firewall and is wholly controlled internally. Private clouds also increase the agility of IT an organization's IT infrastructure and make it easier to roll out new technology projects. Download this eBook to get the facts behind the private cloud and learn how your organization can get started.