
	Where results make sense

Topic: ICCCM

Related Topics

SSI

John Noyes

Tract

NSAIDs

EADS

Hubble Flow

Secrecy

Lee Tenghui

Donbass

1989

Rakino Island

Maglite

Dark Star

Herschel

Wolfville, Nova Scotia

In the News (Fri 13 Nov 09)

Northern Trust

Marvin Harrison

Peter Chernin

Gary Locke

Match Play

Penelope Cruz

Mickey Rourke

AR Rahman

Danny Boyle

Hugh Jackman

	Inter-Client Communication Conventions Manual
		In computing, the Inter-Client Communication Conventions Manual (almost universally referred to by its initials, ICCCM) is a standard for X Window System clients to interoperate on a single server.
		The ICCCM is notorious for being ambiguous and difficult to correctly implement [1] ( http://catalog.com/hopkins/unix-haters/x-windows/disaster.html) [2] ( http://lists.slug.org.au/archives/slug-chat/2001/July/msg00054.html).
		Most X programmers work to the specifications of their widget toolkit or desktop environment rather than directly to the ICCCM.
	www.arikah.net /encyclopedia/ICCCM (211 words)

	Openbox - Wikipedia, the free encyclopedia
		Though this may sacrifice some features present in other window managers, such as menu icons and round window borders, it does support many other features, such as menus by which the user can control applications or which display various dynamic information.
		Openbox is fully ICCCM - and EWMH -compliant.
		Openbox allows the user to have a right-click (or any other bind) "root menu" on the desktop, and allows one to configure the way your windows are managed.
	en.wikipedia.org /wiki/Openbox (303 words)

	X Window System - Wikipedia, the free encyclopedia
		The ICCCM, a specification for client interoperability, is notoriously difficult to implement correctly.
		The performance edge for graphical computing is now in the most advanced graphics functions, which are typically implemented in proprietary drivers written by the manufacturers, and generally for Windows (the largest consumer market) first.
		ICCCM v2.0; Inter-Client Exchange; X Session Management; X Synchronization extension; X Image extension; XTEST extension; X Input; X Big Requests; XC-MISC; XFree86 changes.
	en.wikipedia.org /wiki/X_Windows (3693 words)

	Unix Squeak - and the ICCCM
		There is a document (the "ICCCM" manual) describing the protocol in detail.
		The mechanism is relatively simple, the API is fairly small, the protocol is logical, and the interpretation of the spec was generally accepted for many years (and by the developers of very many X applications that are still in daily use).
		The selection named by the atom PRIMARY is used for all com- mands that take only a single argument and is the principal means of communication between clients that use the selec- tion mechanism.
	www-sor.inria.fr /~piumarta/squeak/icccm.html (1113 words)

	Re: ICCCM compliance?
		But an icon window inherits all the limitations of any other window, meaning that it can't appear in more than one place.
		Since any modern, sane window manager supports icon pixmaps with more than two colors, I chose to violate ICCCM rather than limit what the window manager can do with Eterm's icon.
		ICCCM also dictates that the window manager should not steal key or button events from any other client.
	lists.debian.org /debian-policy/1999/12/msg00053.html (456 words)

	Extended Window Manager Hints
		To fulfill the ICCCM principle that clients should behave the same regardless whether a window manager is running or not, window managers which implement large desktops must interpret all client-provided geometries with respect to the current viewport.
		Both alternatives are completely ICCCM compliant, although the second one may be somewhat problematic for clients trying to figure out the window manager decorations around their toplevel windows and for clients trying to draw background images on the root window.
		It has been noted that this is a slight ICCCM violation, but as this behavior is pretty standard for many toolkits and window managers, and is extremely unlikely to break anything, it seems reasonable to document it as standard.
	standards.freedesktop.org /wm-spec/wm-spec-latest.html (9685 words)

	selection (Site not responding. Last check: 2007-10-08)
		Type specifies the form in which the selection is to be returned (the desired ``target'' for conversion, in ICCCM terminology), and should be an atom name such as STRING or FILE_NAME; see the Inter-Client Communication Conventions Manual for complete details.
		If the selection is returned in a non-string format, such as INTEGER or ATOM, the selection command converts it to string format as a collection of fields separated by spaces: atoms are converted to their textual names, and anything else is converted to hexadecimal integers.
		The format argument specifies the representation that should be used to transmit the selection to the requester (the second column of Table 2 of the ICCCM), and defaults to STRING.
	www.cse.unsw.edu.au /~geoffo/info/gcl-tk/selection.html (713 words)

	[forum] A Call For Open Governance Of X Development
		ICCCM is a standard owned and managed by X.Org.
		Formally changing ICCCM isn't the same thing as creating something new like Render, which is a disjoint extension.
		Yet another avenue would be to say "ICCCM is what it is, we're going to define something new, called ICCCM++, which is a superset of ICCCM v, but we'll go do our own thing, and ICCCM can go do its own thing, and maybe we'll sync up later".
	www.xfree86.org /pipermail/forum/2003-March/002415.html (883 words)

	Making use of the ICCCM Pt1: Requestor Side Selections
		This is the first installment on a series about the ICCCM (Inter-Client Communication Conventions Manual) which is a manual for client communication in the X environment.
		The ICCCM is very important to us because it defines some ways in which clients can communicate, without which it would be very difficult to share anything between clients, especially when you consider that clients are quite often not even on the same machine as the one they want to talk to.
		The ICCCM makes extreme use of properties and atoms, which is why the first chapter is devoted to their explanation.
	www.gmonline.demon.co.uk /cscene/CS7/CS7-06.html (3007 words)

	fvwm focusing problem (Site not responding. Last check: 2007-10-08)
		In addition, ICCCM states that it should be possible for applications to receive ANY keystroke, which is not consistent with the key- board shortcut approach used in fvwm and most other window managers.
		The ICCCM states that windows possessing the property WM_HINTS(WM_HINTS): Client accepts input or input focus: False should not be given the keyboard input focus by the window manager.
		I wonder if this problem is caused by running fvwm in a vncviewer that is handled by a local fvwm (which I am currently doing), and if a fix is available in other window managers, and lastly, if this is something that can be (or should be) fixed in the vnc viewer itself.
	www.realvnc.com /pipermail/vnc-list/2000-September/016923.html (373 words)

	ICCCM (Site not responding. Last check: 2007-10-08)
		It explains how to use the X selection mechanism, how to interact with the Window manager (and what a window manager is), session management, and how to manage shared resources like the keyboard focus and colormap s.
		The Tk toolkit handles most of the ICCCM conventions internally, so as an application writer you don't need to worry about it too much.
		In short, no. However, it is possible to make Tk more ICCCM compliant through the use of a few wm methods.
	wiki.tcl.tk /ICCCM (188 words)

	[No title] (Site not responding. Last check: 2007-10-08)
		Cc: bug-lucid-emacs@lucid.com Well, I went and read the ICCCM (again) since we last spoke, and I'm going to stand by my claim that my patch is ICCCM compliant.
		In section 4.1.7 of ICCCM version 1.1 distributed with X11R5, it says that a locally active client "expects keyboard input and explicitly sets the input focus, but only does so when one of its windows already has the focus" -- I am not reading this as "...
		I hope that, at a bare minimum, I've convinced you that my patch did not deserve to be condemned, and that its claims to ICCCM compliance are certainly not based upon "no observed ill effects"...
	www.cs.cmu.edu /afs/cs.cmu.edu/project/gwydion-1/OldFiles/temp/1955 (630 words)

	Components of GUI environments
		Users expect to be able, at a minimum, to be able to use the mouse to copy or cut text from one application window and paste it into another.
		ICCCM also allows applications to post hints to a window manager about the preferred locations, sizes, stacking behavior, and other properties of their windows.
		ICCCM alone will not enable this; it requires something like an object-broker daemon running in background, and a GUI-environment-specific notification protocol that tells applications when they need to query the daemon.
	www.catb.org /~esr/writings/taouu/html/ch03s04.html (904 words)

	RE: ICCCM breakage, IconicState, and desktops
		If somebody does indeed go the way of virtual desktops without virtual roots, then the only choice they have is to be slightly ICCCM uncompliant and unmap only frame window, but not the client.
		The only reason _NET_WM_STATE is there is only to compliment the 3 ICCCM state, and allow for things like maximized and shaded, which is not covered by ICCCM.
		Remeber - we don't override ICCCM - we complimnent it.
	mail.gnome.org /archives/wm-spec-list/2001-December/msg00007.html (596 words)

	Diary for auspex
		Menus make a lousy user interface and there are so many ways to make them worse.
		The most recent copyright on the ICCCM is 1994.
		Sometime in 2002, a window manager may have, for the first time, full ICCCM 2.0 compliance.
	www.advogato.org /person/auspex/diary.html?start=5 (1245 words)

	Re: ICCCM breakage, IconicState, and desktops
		IconicState is defined in the ICCCM to be ambiguous.
		The ICCCM says (section 4.1.4) that the "top-level window is iconic (whatever that means for this window manager)" and that WM_ICON_NAME can be displayed instead of icon_pixmap or icon_window.
		The ICCCM simply defines it as any state where the client window is unmapped.
	mail.gnome.org /archives/wm-spec-list/2001-December/msg00020.html (801 words)

	10) What is the ICCCM? (How do I write X-friendly applications?) (Site not responding. Last check: 2007-10-08)
		If you are writing X clients, you need to read and understand the ICCCM, in particular the sections discussing the selection mechanism and the interaction between your client and the window manager.
		Alternate definition: the ICCCM is generally the M in "RTFM" and is the most-important of the least-read X documents.
		Get the ICCCM from these sources: - Version 2.0 of the ICCCM is an X Consortium standard as of R6.
	www.faqs.org /faqs/x-faq/part1/section-11.html (283 words)

	motif-faq-part5 (Site not responding. Last check: 2007-10-08)
		This information is contained in the WM_STATE property but ordinary clients are not supposed to look at that (its values have not yet been standardised).
		Movement between the three states is standardised by ICCCM.
		ICCCM compliant window managers will map windows in changing them to normal state and unmap them in changing them to iconic state.
	www.robotic.dlr.de /~smagt/computing/motif-faq-part5.html (6594 words)

	Window Managers, ICCCM, and Shells (Site not responding. Last check: 2007-10-08)
		ICCCM defines protocols for communication between clients and window managers.
		ICCCM recognizes four models for the relationship between clients and window managers in setting input focus:
		The client does not expect keyboard input and does not want the window manager to set focus to any of its windows.
	docs.hp.com /en/B1171-90145/ch18s01.html (3599 words)

	ðÒÏÅËÔ OpenNet: MAN DtDndProtocol (4) óÐÅÃÉÁÌØÎÙÅ ÆÁÊÌÙ /dev/* (FreeBSD É Linux)
		The transfer is accomplished using X selections and is controlled by the drop receiver.
		For most data transfers, this is accomplished by converting the selection into the ICCCM DELETE target to tell the drag initiator that it may delete the data.
		The drop receiver may alternatively choose to use the ICCCM DELETE target to com- plete the XmDROP_MOVE and the drag initiator must be ready to comply.
	www.opennet.ru /man.shtml?topic=DtDndProtocol&category=4&russian=4 (1153 words)

	[No title]
		The suggested addition of UTF8_STRING to ICCCM is detailed in http://www.cl.cam.ac.uk/~mgk25/ucs/icccm.diff The new parts 13/14/15 of ISO 8859 are listed in the ISO Catalogue on http://www.iso.ch/isob/switch-engine-cate.pl?searchtype=refnumber&KEYWORDS=8859 and are already implemented in XFree86 4.0.2 and the revised BDF fonts.
		In general, private selection names should start with a leading underscore, followed by the organizational prefix, followed by another underscore.
		In general, private protocols should start with a leading underscore, followed by the organizational prefix, followed by another underscore.
	www.cl.cam.ac.uk /~mgk25/ucs/registry.diff (198 words)

	Fvwm / ICCCM Compliance (Site not responding. Last check: 2007-10-08)
		As of this (1.20l) colormap handling is not completely ICCCM compliant.
		In addition, ICCCM states that it should be possible for applications to receive ANY keystroke, which is not consistent with the keyboard shortcut approach used in fvwm and most other window managers.
		Window positioning has been a sticking point for fvwm in releases prior to about 1.20i.
	www.ida.liu.se /imported/fvwm/icccm.html (74 words)

	ICCCM - Footnotes
		This obsolete protocol was described in the July 27, 1988 draft of the ICCCM.
		If this selection is owned, clients may assume that the window manager complies with ICCCM version 2.0 or later.
		This convention has changed since earlier drafts because of the introduction of the protocol in the next section.
	www.talisman.org /icccm/footnotes.html (666 words)

	Command line options (Site not responding. Last check: 2007-10-08)
		has the ability to recognize and replace other (fully) icccm compliant window managers.
		However the default behaviour is not to replace other window managers since these programs usually will be terminated then which will also terminate the whole X-session in most cases (which shouldn't be done accidentally playing around with
		This option uses the protocol specified by icccm 2.0 to make another window manager terminate and pass control to
	udeproject.sourceforge.net /Documentation/node7.html (157 words)

	Re: [gtk-list] Re: ICCCM compliance of GTK...
		Subject : Re: [gtk-list] Re: ICCCM compliance of GTK...
		:) -> -> What I meant was that for what the ICCCM does _not_ require the -> client to respond to WM_TAKE_FOCUS, when wm_hints->input is true.
		-> -> However, the ICCCM implies that one is not supposed to use -> CurrentTime.
	lists.gnome.org /archives/gtk-list/1998-April/msg00275.html (712 words)

	Diary for auspex
		They both rely on what's in the ICCCM and judicious window management policies.
		The ICCCM revision history seems to indicate that both methods have been possible since 1989, when ICCCM version 1.0 was released.
		I wish people would stop trying to kluge over systemic bugs and start fixing the bugs that stand in the way of fixing them.
	www.advogato.org /person/auspex/diary.html?start=63 (2335 words)

	freedesktop.org - Standards/ClipboardsWiki
		Historically, X clients have not handled cut-and-paste in a consistent way, leading users to believe that X doesn't even have a working clipboard.
		X has a thing called "selections" which are just clipboards, essentially (implemented with an asynchronous protocol so you don't actually copy data to them).
		In addition, the ICCCM has a thing called "cut buffers" which most clients no longer support.
	freedesktop.org /Standards/ClipboardsWiki (757 words)

	Enlightenment Frequently Asked Questions: Manager Issues
		This probably one of the more important aspects of ICCCM, as the window tells the window manager which direction to "gravitate" towards when it is dealing with an overlap.
		North is towards the top of your window, and the rest of the compass follows accordingly.
		This means that some windows that you spawn that do not ask for "hands off treatment" as well will be placed or fitted over the GNOME Panel.
	plumeria.vmth.ucdavis.edu /info/enlightenment/faq-7.html (641 words)

	Window Manager Flames
		I39L is a hash for the acronymic expansion of ICCCM for "Inter-Client Communication Conventions Manual".
		The NeWS people wanted to do it the other way around, and prototyped an ICCCM window manager in NeWS (mostly object oriented PostScript, and a tiny bit of C), that wrapped X windows up in NeWS window frames.
		There is no need for such "ICCCM compliant" behavior with TNT menus.
	home.hccnet.nl /j.bus/unix-haters/x-windows/i39l.html (3390 words)

Try your search on: Qwika (all wikis)