X window manager

X window manager

From Wikipedia, the free encyclopedia

An X window manager is a window manager which runs on top of the X Window System, a windowing system mainly used on Unix-like systems.

Unlike the Mac OS (Apple Macintosh) and Microsoft Windows platforms (excepting Microsoft Windows explorer.exe shell replacements) which have historically provided a vendor-controlled, fixed set of ways to control how windows and panes display on a screen, and how the user may interact with them, window management for the X Window System was deliberately kept separate from the software providing the graphical display. The user can choose between various third-party window managers, which differ from one another in several ways, including:

  • customizability of appearance and functionality:
  • consumption of memory and other system resources
  • degree of integration with a desktop environment, which provides a more complete interface to the operating system, and provides a range of integrated utilities and applications.

Contents

   [hide

[edit]How X window managers work

When a window manager is running, some kinds of interaction between the X server and its clients are redirected through the window manager. In particular, whenever an attempt to show a new window is made, this request is redirected to the window manager, which decides the initial position of the window. Additionally, most modern window managers are reparenting, which usually leads to a banner being placed at the top of the window and a decorative frame being drawn around the window. These two elements are controlled by the window manager rather than the program. Therefore, when the user clicks or drags these elements, it is the window manager that takes the appropriate actions (such as moving or resizing the window).

Window managers are also responsible for icons. Indeed, icons do not exist at the X Window System core protocol level. When the user requests a window to be iconified, the window manager unmaps it (makes it non-visible) and takes the appropriate actions to show an icon in its place. Most modern window managers do not literally show icons to represent iconified windows anymore. Often, an auxiliary toolbar program will allow access to iconified windows.

While the main aim of a window manager is to manage the windows, many window managers have additional features such as handling mouse clicks in the root window, presenting panes and other visual elements, handling some keystrokes (e.g., Alt-F4 may close a window), deciding which application to run at start-up, etc.

Standardized protocols exist to allow normal clients to communicate with the window manager. The original one is Inter-Client Communication Conventions Manual (ICCCM) but this has been superseded by the Extended Window Manager Hints (EWMH).

[edit]Types of window managers

[edit]Stacking window managers

stacking window manager renders the windows one-by-one onto the screen at specific co-ordinates. If one window's area overlaps another, then the window "on top" overwrites part of the other's visible appearance. This results in the appearance familiar to many users in which windows act a little bit like pieces of paper on a desktop, which can be moved around and allowed to overlap.

In contrast to compositing window managers (see below), the lack of separate offscreen buffers can mean increased efficiency, but effects such as translucency are not possible.

Stacking window managers include AmiwmBlackboxEnlightenmentevilwmFluxboxFVWMIceWMMWMOpenbox and Window Maker.

[edit]Tiling window managers

tiling window manager is a window manager with an organization of the screen into mutually non-overlapping frames (hence the nametiling), as opposed to the traditional approach of coordinate-based stacking of objects (windows) that tries to emulate the desk paradigm.

Tiling window managers include awesomedwmIonlarswmratpoisonStumpwmwmiixmonad, and XWEM.

[edit]Compositing window managers

compositing window manager may appear to the user similar to a stacking window manager. However, the individual windows are first rendered in individual buffers, and then their images are composited onto the screen buffer; this two-step process means that visual effects (such as shadows, translucency) can be applied. It also means that compositing window managers tend to be more resource-hungry than stacking window managers.

Compositing window managers include BerylCompizKWin (since 4.0), Metacity (since 2.20), Mutter and Xfwm.

[edit]Virtual window managers

virtual window manager is a window manager that uses virtual screens, whose resolution can be higher than the resolution of one's monitor/display adapter thus resembling a two dimensional virtual desktop with its viewport. This environment is very useful when one wishes to have a large number of windows open at the same time. A number of virtual window managers have been made, including FVWM,TvtwmHaZe and others.

[edit]Window managers that are extensible

Some window managers are extensible, or programmable, by user scripts. For example, Sawfish with rep, a lisp dialect, Xmonad by haskell, etc.

In these window managers, users can define or override reactions to window size and position changes, window creation and deletion, key and mouse input, timer, etc. They often provide on-the-fly code execution, too.

[edit]X window managers

[edit]See also

[edit]References

[edit]External links



View page ratings
Rate this page
Trustworthy
Objective
Complete
Well-written

评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值