Windowing system
This article needs additional citations for verification. (December 2019) |
In
Each currently running
Technical details
The main component of any windowing system is usually called the
From a programmer's point of view, a windowing system implements graphical primitives. For example: rendering fonts or drawing a line on the screen. It provides an abstraction of the graphics hardware for use by higher-level elements of the graphical interface such as a window manager.[citation needed]
A display server protocol can be network capable or even network transparent, facilitating the implementation of thin clients.[citation needed]
Display server
A display server or window server is a program whose primary task is to coordinate the input and output of its clients to and from the rest of the operating system, the hardware, and each other. The display server communicates with its clients over the display server protocol, a
The display server is a key component in any graphical user interface, specifically the windowing system.
The server/client relationship of a standalone display server is somewhat counterintuitive in that a "server" is usually thought of as a large, remote machine, whereas a standalone "display server" is a small local system, with most clients being executed on a larger central machine. The explanation is that a display server provides the services of a display and input devices.
Display server communications protocols
X11
One example of a display server is the
One of the implementations of display server concept is
Notable examples of display servers implementing the X11 display server protocol are X.Org Server, XFree86, XQuartz and Cygwin/X, while client libraries implementing the X11 display server protocol are Xlib and XCB.
Wayland
Display servers that implement the Wayland display server protocol are called
.Wayland compositors communicate with Wayland clients over the
Wayland is used to a certain degree in some Linux desktop distributions, such as
An implementation of Wayland is available under the MIT License, the libwayland-client and libwayland-server libraries.
There is an ongoing effort to add Wayland support to ChromeOS.[2]
Mir
The
There are implementations of the Mir display server, the libmir-server and the libmir-client libraries available under the
Windowing systems with APIs
SurfaceFlinger
Google developed a display server called SurfaceFlinger[3] for Android (another Linux kernel-based operating system primarily for mobile devices):
Everything in Android is rendered to a "surface"; "surfaces" are produced by applications and placed into a queue that is managed by SurfaceFlinger.[4][5]
Yet another Android-specific solution is "Gralloc". Gralloc handles device memory i.e. it does allocation, arbitration, it handles synchronization via Android/Linux fence file descriptors. Gralloc competes with other solutions like e.g. Mesa's
For compositing in Android, Surfaces are sent to SurfaceFlinger, which uses OpenGL ES to do the compositing.
Hardware Composer HAL (HWC) was introduced in Android 3.0 and has evolved steadily over the years. Its primary purpose is to determine the most efficient way to composite buffers with the available hardware. As a HAL, its implementation is device-specific and usually done by the display hardware OEM.
Quartz Compositor
For Apple's macOS family of operating systems, Quartz Compositor fulfils the tasks of a display server and of a window manager in the windowing system.
Desktop Window Manager
For Microsoft Windows, from Windows Vista onward, Desktop Window Manager enables the use of hardware acceleration to render the graphical user interface. It was originally created to enable portions of the new "Windows Aero" user experience, which allowed for effects such as transparency, 3D window switching and more. It is also included with Windows Server 2008, but requires the "Desktop Experience" feature and compatible graphics drivers to be installed. From Windows 8 onwards DWM can't be disabled and is software rendered if no suitable graphics card is installed.
List of windowing systems
For Unix-like operating systems
- fbui (with a modified Linux kernel)
- HP Windows/9000 (on early versions of HP-UX)[6]
- CMU Andrew Window Manager[7]
- Sapphire[8] for the PERQ
- Whitechapel Oriel[9]
- Silicon Graphics MEX
- ManaGeR (MGR)
- Metisse
- Mir
- NeWS / OpenWindows
- NeXT DPS
- Orbital (Redox)
- Qt Extended
- Quartz Compositor (macOS)
- SunView
- Twin (Text WINdows)
- W Window System
- Wayland
- X Window System
- XFast
- Xynth
For Windows NT-family operating systems
- Desktop Window Manager (DWM) in Microsoft Windows (Vista and later)
- ReactOS Explorer
- Classic Shell
- Pokki
- RetroUI
Web windowing systems
- Dojo
- ExtJS
- TIBCOGeneral Interface
- Web Window Manager
Other
- DM
- GEM
- Intuition
- Microwindows
- MiniGUI
- OOHG
- Visi On
- VWS (VAX Workstation Software)
- mpx/mux (for the Bell Labs Blit terminal)
- Symbolics Dynamic Windows
Some systems such as
See also
References
- ISBN 9780824727178. Retrieved 8 June 2017.
- ^ "Ozone Overview". Retrieved 2017-08-20.
- ^ "Android system architecture" (PDF). Archived from the original (PDF) on 2016-04-08.
- ^ "Android Developer: Surface".
- ^ "Android Developer: SurfaceFlinger and Hardware Composer".
- ^ "HP Windows/9000 User's Manual" (PDF). Hewlett Packard. April 1988. Retrieved 2021-10-26.
- ^ "Andrew: A Distributed Personal Computing Environment" (PDF). Communications of the ACM. 29 (3). March 1986.
- S2CID 11138733.
- ^ "Chilton::INF::Window Management". www.chilton-computing.org.uk. Retrieved 2023-04-11.