Inter-Client Communication Conventions Manual
It is proposed that this article be deleted because of the following concern:
If you can address this concern by improving, copyediting, sourcing, renaming, or merging the page, please edit this page and do so. You may remove this message if you improve the article or otherwise object to deletion for any reason. Although not required, you are encouraged to explain why you object to the deletion, either in your edit summary or on the talk page. If this template is removed, do not replace it. This message has remained in place for seven days, so the article may be deleted without further notice. Find sources: "Inter-Client Communication Conventions Manual" – news · newspapers · books · scholar · JSTOR Nominator: Please consider notifying the author/project: {{subst:proposed deletion notify|Inter-Client Communication Conventions Manual|concern=Only passing mentions in sources and literature; not notable.}} ~~~~Timestamp: 20180912104601 10:46, 12 September 2018 (UTC) Administrators: delete |
In computing, the Inter-Client Communication Conventions Manual (ICCCM or I39L short for "I", 39 letters and "L")[1] is a standard protocol for the X Window System. It specifies communication for clients of a common X server. It is primarily used for communication between the window manager and the X server's other clients.
History
It was designed by David S. H. Rosenthal of the MIT X Consortium in 1988.
Version 1.0 was released in July 1989 and version 2.0 in early 1994.
![[icon]](/wiki/File:Wiki_letter_w_cropped.svg?lang=en){kind=small} | This section needs expansion. You can help by adding to it. (December 2016) |
Background
X deliberately specifies "mechanism, not policy" for how windows interact. As such, an additional specification beyond the X protocol itself was needed for client interoperation.
Features
The ICCCM specifies cut and paste buffers, window manager interaction, session management, how to manipulate shared resources and how to manage device colours. These low-level functions are generally implemented[why?] within widget toolkits or desktop environments. This isolates application programmers from working directly with the ICCCM itself, as this functionality is delegated to the implementing toolkit.
| This section needs expansion. You can help by adding to it. (December 2016) |
Criticism
 |
The ICCCM is notorious for being ambiguous and difficult to correctly implement.[2] Furthermore, some parts are obsolete or no longer practical to implement.[3]
Efforts to update and clarify the ICCCM for current needs have resulted in the Extended Window Manager Hints (EWMH), which has gained fairly broad acceptance and continues to be extended as the need arises.[citation needed]
List of Window Managers that are ICCCM Compliant
 |
- aewm — a stacking window manager.
- alloywm — partial compliance.
- awesome — a dynamic window manager that is configured in Lua.
- blackbox (version 0.65 and later) — a stacking window manager that was later discontinued.
- Compiz
- dwm — can be configured for compliance
- enlightenment — also serves as a Wayland compositor.
- evilwm — partial compliance
- fvwm
- IceWM
- KWin — default window manager and Wayland compositor of KDE Plasma.
- Metacity — default window manager of GNOME 2.
- musca
- Openbox — the default window manager used by LXDE and LXQt.
- vtwm
- wmfs
- xfwm
- xmonad
References
External links
- Inter-Client Communication Conventions Manual, Version 2.0
- Inter-Client Communication Conventions Manual Version 2.0
| Architecture |  | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Extensions | |||||||||||||||
| Components and notable implementations |
| ||||||||||||||
| Standards | |||||||||||||||
| Applications | |||||||||||||||