1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Using GTK+ on the X Window System</title>
<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
<link rel="home" href="index.html" title="GTK+ Reference Manual">
<link rel="up" href="gtk.html" title="Part I. GTK+ Overview">
<link rel="prev" href="gtk-running.html" title="Running GTK+ Applications">
<link rel="next" href="gtk-windows.html" title="Using GTK+ on Windows">
<meta name="generator" content="GTK-Doc V1.14 (XML mode)">
<link rel="stylesheet" href="style.css" type="text/css">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="2"><tr valign="middle">
<td><a accesskey="p" href="gtk-running.html"><img src="left.png" width="24" height="24" border="0" alt="Prev"></a></td>
<td><a accesskey="u" href="gtk.html"><img src="up.png" width="24" height="24" border="0" alt="Up"></a></td>
<td><a accesskey="h" href="index.html"><img src="home.png" width="24" height="24" border="0" alt="Home"></a></td>
<th width="100%" align="center">GTK+ Reference Manual</th>
<td><a accesskey="n" href="gtk-windows.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
</tr></table>
<div class="refentry" title="Using GTK+ on the X Window System">
<a name="gtk-x11"></a><div class="titlepage"></div>
<div class="refnamediv"><table width="100%"><tr>
<td valign="top">
<h2><span class="refentrytitle">Using GTK+ on the X Window System</span></h2>
<p>Using GTK+ on the X Window System —
X11 aspects of using GTK+
</p>
</td>
<td valign="top" align="right"></td>
</tr></table></div>
<div class="refsect1" title="GTK+ for the X Window System">
<a name="id389088"></a><h2>GTK+ for the X Window System</h2>
<p>
On UNIX, the X backend is the default build for GTK+. So
you don't need to do anything special when compiling it,
and everything should "just work."
</p>
<p>
To mix low-level Xlib routines into a GTK program,
see <GTKDOCLINK HREF="gdk-X-Window-System-Interaction">GDK X Window
System interaction</GTKDOCLINK> in the GDK manual.
</p>
<div class="refsect2" title="X11-specific commandline options">
<a name="x11-cmdline"></a><h3>X11-specific commandline options</h3>
<p>
The X backend understands some additional command line
arguments.
</p>
<p title="--display display"><b><code class="systemitem">--display <em class="replaceable"><code>display</code></em></code>. </b>
The name of the X display to open instead of the one specified
in the <code class="envar">DISPLAY</code> environment variable.
</p>
<p title="--screen screen_number"><b><code class="systemitem">--screen <em class="replaceable"><code>screen_number</code></em></code>. </b>
The number of the screen within the default display. This overrides
any screen number specified in the display name specified by
by he <code class="systemitem">--display</code> command line option or
the <code class="envar">DISPLAY</code> environment variable. If this screen
cannot be opened, then GTK+ will fall back to the screen
specified in the display name. This option is not useful
interactively; the intended purposes is that when a program
registers its command line with a <em class="firstterm">session
manager</em> for later restarting, it can save the
screen it is on, without having to worry if it might be
restarted on a different display.
</p>
<p title="--sync"><b><code class="systemitem">--sync</code>. </b>
Makes all X requests synchronously. This is a useful option for
debugging, but it will slow down the performance considerably.
</p>
<p title="--gxid-host host"><b><code class="systemitem">--gxid-host <em class="replaceable"><code>host</code></em></code>. </b>
The host to contact the <span class="application">gxid</span> daemon on; overrides
the <a class="link" href="gtk-x11.html#GXID" title="GXID_HOST, GXID_PORT"><code class="envar">GXID_HOST</code></a> environment variable.
</p>
<p title="--gxid-port port"><b><code class="systemitem">--gxid-port <em class="replaceable"><code>port</code></em></code>. </b>
The port for the connection to <span class="application">gxid</span>; overrides
the <a class="link" href="gtk-x11.html#GXID" title="GXID_HOST, GXID_PORT"><code class="envar">GXID_PORT</code></a> environment variable.
This option is only available if GTK+ has been configured with
<code class="option">--gdk-target=x11</code>.
</p>
</div>
<hr>
<div class="refsect2" title="X11-specific environment variables">
<a name="x11-envar"></a><h3>X11-specific environment variables</h3>
<p>
The X backend can be influenced with some
additional environment variables.
</p>
<p title="GXID_HOST, GXID_PORT"><a name="GXID"></a><b><code class="envar">GXID_HOST</code>, <code class="envar">GXID_PORT</code>. </b>
The host and port to contact the <span class="application">gxid</span> daemon
on. <span class="application">gxid</span> is only necessary on X servers which
don't support using the pointer and extension devices at once, and is
only built if GTK+ is configured with <code class="option">--with-xinput=gxi</code>.
The <span class="application">XFree86</span> and <span class="application">Xorg</span>
X servers don't have this
restriction.
</p>
<p title="GDK_USE_XFT"><b><code class="envar">GDK_USE_XFT</code>. </b>
If this variable is set to 1, GTK+ will use the Pango Xft backend instead
of the X backend when possible (i.e. when the X server supports the XRender
extension and Pango has been built with Xft support).
</p>
</div>
</div>
<div class="refsect1" title="Understanding the X11 architecture">
<a name="gtk-X11-arch"></a><h2>Understanding the X11 architecture</h2>
<p>
People coming from a Windows or MacOS background often find certain
aspects of the X Window System surprising. This section introduces
some basic X concepts at a high level. For more details, the book most
people use is called the <em class="citetitle">Xlib Programming
Manual</em> by Adrian Nye; this book is volume one in the
O'Reilly X Window System series.
</p>
<p>
Standards are another important resource if you're poking in low-level
X11 details, in particular the ICCCM and the Extended Window Manager
Hints specifications. <a class="ulink" href="http://www.freedesktop.org/standards/" target="_top">freedesktop.org</a>
has links to many relevant specifications.
</p>
<p>
The GDK manual covers <GTKDOCLINK HREF="gdk-X-Window-System-Interaction">using Xlib in a GTK
program</GTKDOCLINK>.
</p>
<div class="refsect2" title="Server, client, window manager">
<a name="id391733"></a><h3>Server, client, window manager</h3>
<p>
Other window systems typically put all their functionality in the
application itself. With X, each application involves three different
programs: the <em class="firstterm">X server</em>, the application (called
a <em class="firstterm">client</em> because it's a client of the X
server), and a special client called the <em class="firstterm">window
manager</em>.
</p>
<p>
The X server is in charge of managing resources, processing drawing
requests, and dispatching events such as keyboard and mouse events to
interested applications. So client applications can ask the X server
to create a window, draw a circle, or move windows around.
</p>
<p>
The window manager is in charge of rendering the frame or borders
around windows; it also has final say on the size of each window,
and window states such as minimized, maximized, and so forth.
On Windows and MacOS the application handles most of this.
On X11, if you wish to modify the window's state, or
change its frame, you must ask the window manager to do so on your
behalf, using an established <a class="ulink" href="http://www.freedesktop.org/standards/" target="_top">convention</a>.
</p>
<p>
GTK+ has functions for asking the window manager to do various things;
see for example <a class="link" href="GtkWindow.html#gtk-window-iconify" title="gtk_window_iconify ()">gtk_window_iconify()</a> or <a class="link" href="GtkWindow.html#gtk-window-maximize" title="gtk_window_maximize ()">gtk_window_maximize()</a> or <a class="link" href="GtkWindow.html#gtk-window-set-decorated" title="gtk_window_set_decorated ()">gtk_window_set_decorated()</a>.
Keep in mind that <a class="link" href="GtkWindow.html#gtk-window-move" title="gtk_window_move ()">gtk_window_move()</a> and window sizing
are ultimately controlled by the window manager as well and most
window managers <span class="emphasis"><em>will</em></span> ignore certain requests from
time to time, in the interests of good user interface.
</p>
</div>
</div>
</div>
<div class="footer">
<hr>
Generated by GTK-Doc V1.14</div>
</body>
</html>
|
