|
A desktop environment is a collection of software designed to give functionality and a certain look and feel to an operating system. This article applies to operating systems which are capable of running the X Window System such as Linux, BSD, and Mac OS X.[1] Microsoft Windows is incapable of natively running the X Window system; however, third party X servers like Cygwin/X or Xming are available for Microsoft Windows which make the system capable of running the X Window system.[2][3]
Elements of a desktop environmentA desktop environment (DE) can be broken up into several components that function independently and interact with one another to provide the look and feel and functionality of the desktop environment. A fundamental part of a DE is the window manager or WM. A window manager creates a certain way for application windows to present themselves to the user. It manages the various application windows, keeping track of which ones are open and providing features to switch between them. Another important element of a DE is the file manager. This application manages files/ folders and presents them in a way that the user finds convenient. It provides file operations like viewing, copying or moving, changing permissions and deleting. DEs usually provide utilities to set wallpapers and screensavers, display icons on the desktop, and perform some administrative tasks. They may optionally include word processors, CD/DVD writing applications, web browsers and e-mail clients. Some exceptions must be noted here. Window managers like Fluxbox, wmii and Ratpoison operate independently of a desktop environment and were written with this objective in mind. Additional hand-picked applications add functionality such as a panel and volume management which gives them some of the qualities of a full DE. This contrasts the behaviour of WMs like Metacity and KWin which were not written with the objective of operating independently of a DE. KDE and GNOME are written almost completely on special software libraries Qt and GTK respectively.[4] This usually means that virtually every component of the desktop environment including the file manager explicitly depends on that library for its functioning. Obviously, nothing prevents the user from installing any number of software libraries of his/her choice. In practice, software written on major libraries can be run under any desktop environment. Running a package designed for one desktop (which essentially means that it's written using the same libraries as the desktop itself is) within a different desktop can be visually displeasing, as well as incurring the RAM penalty of loading libraries that wouldn't otherwise be required. Choosing the right desktop environment is essential to ensure streamlined work flow. Some of the differences influencing a choice are:
Desktop comparison informationOuter view of different classes of desktop environmentsFor convenience, the desktop environments have been classified into five classes only for the purpose of representation in this table. The classes are listed approximately in the order magnitude of size of project. Note that many desktop environments are not in the table, but nearly all desktop environments should fall into one of the five categories. The table also includes X window managers which are not desktop environments, but often mistaken for same.
Memory comparison can be found here. Default programs packagedThis table shows basic information on the default programs of some desktop environments for the X Window System: Comparison of ease of use and stability
GNOME's graphical file manager Nautilus is very easy to use and is packed with a lot of features making it easy for new Linux users to easily pick up and understand its working.[16] KDE's Konqueror is also very easy to use, both as a file manager and as a web browser.[17] However this ease of use comes at a price, as both Nautilus and Konqueror are noticeably slower than lighter weight file managers. Some users object to their multifarous nature as both local file browser and remote client, fearing security issues and preferring a more minimalist approach. Both GNOME and KDE come with many pre-packaged graphical configuration tools, reducing the need to manually edit configuration files for new users. They have extensive bundled software such as graphical menu editors, text editors, audio players, and software for doing administrative work. All applications installed in most distributions are automatically added to the GNOME and KDE menus. No major configuration changes are necessary to begin working. However, by using graphical tools, the extent to which the desktops can be configured is determined by the power provided by those tools. Blackbox, Fluxbox, Ratpoison, Ion and wmii require users to edit configuration files by hand to configure virtually every aspect of the desktop environment and are hence highly configurable. A new user, however, may feel uncomfortable without any graphical tools. These window managers also do not provide any additional software like file managers, text editors or web browsers, leaving it up to their users to decide upon the software they prefer.[18] Some users state they prefer these desktops over traditional "bloated" desktops as they claim it increases their productivity significantly.[citation needed] Compatibility and interoperability issuesAlthough there are some major issues with using some applications made for KDE on GNOME and vice versa, they are likely to be ironed out in the future. An example of such an issue would be using k3b on GNOME and using the "Send to trash" feature from the interface. The feature fails due to the simple fact that GNOME and KDE don't use the same trash:// protocols. Some desktop environments claim that they support applications made for other desktops explicitly. For example, Fluxbox states KDE support in its feature list.[19] Using software made specifically for the desktop environment in use or Window Manager agnostic software is a way to avoid these issues. For software developers, the Portland Project has released a set of common interfaces that allows applications to integrate across many desktop environments.[20] See also
Notes
References
External links
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
This article is from Wikipedia. All text is available under the terms of the GNU Free Documentation License.
Mercedes Car
This site monitored by SitePinger.net