|
Server : Apache/2.2.17 (Unix) mod_ssl/2.2.17 OpenSSL/0.9.8e-fips-rhel5 DAV/2 PHP/5.2.17 System : Linux localhost 2.6.18-419.el5 #1 SMP Fri Feb 24 22:47:42 UTC 2017 x86_64 User : nobody ( 99) PHP Version : 5.2.17 Disable Function : NONE Directory : /usr/share/gtk-doc/html/gtk/ |
Upload File : |
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Glossary</title>
<meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
<link rel="start" href="index.html" title="GTK+ Reference Manual">
<link rel="up" href="index.html" title="GTK+ Reference Manual">
<link rel="prev" href="gtk-update-icon-cache.html" title="gtk-update-icon-cache">
<link rel="next" href="ix01.html" title="Index">
<meta name="generator" content="GTK-Doc V1.6 (XML mode)">
<link rel="stylesheet" href="style.css" type="text/css">
<link rel="part" href="gtk.html" title="Part I. GTK+ Overview">
<link rel="part" href="gtkbase.html" title="Part II. GTK+ Core Reference">
<link rel="part" href="gtkobjects.html" title="Part III. GTK+ Widgets and Objects">
<link rel="chapter" href="ch01.html" title="Object Hierarchy">
<link rel="chapter" href="ch02.html" title="Widget Gallery">
<link rel="chapter" href="WindowWidgets.html" title="Windows">
<link rel="chapter" href="DisplayWidgets.html" title="Display Widgets">
<link rel="chapter" href="ButtonWidgets.html" title="Buttons and Toggles">
<link rel="chapter" href="NumericEntry.html" title="Numeric/Text Data Entry">
<link rel="chapter" href="TextWidgetObjects.html" title="Multiline Text Editor">
<link rel="chapter" href="TreeWidgetObjects.html" title="Tree, List and Icon Grid Widgets">
<link rel="chapter" href="MenusAndCombos.html" title="Menus, Combo Box, Toolbar">
<link rel="chapter" href="Actions.html" title="Action-based menus and toolbars">
<link rel="chapter" href="SelectorWidgets.html" title="Selectors (File/Font/Color/Input Devices)">
<link rel="chapter" href="LayoutContainers.html" title="Layout Containers">
<link rel="chapter" href="Ornaments.html" title="Ornaments">
<link rel="chapter" href="ScrollingWidgets.html" title="Scrolling">
<link rel="chapter" href="Printing.html" title="Printing">
<link rel="chapter" href="MiscObjects.html" title="Miscellaneous">
<link rel="chapter" href="AbstractObjects.html" title="Abstract Base Classes">
<link rel="chapter" href="PlugSocket.html" title="Cross-process Embedding">
<link rel="chapter" href="SpecialObjects.html" title="Special-purpose features">
<link rel="chapter" href="RecentDocuments.html" title="Recently Used Documents">
<link rel="chapter" href="DeprecatedObjects.html" title="Deprecated">
<link rel="part" href="migrating.html" title="Part IV. Migrating from Previous Versions of GTK+">
<link rel="chapter" href="gtk-migrating-checklist.html" title="Migration Checklist">
<link rel="chapter" href="gtk-migrating-GtkFileChooser.html" title="Migrating from GtkFileSelection to GtkFileChooser">
<link rel="chapter" href="gtk-migrating-GtkAction.html" title="Migrating from old menu and toolbar systems to GtkAction">
<link rel="chapter" href="gtk-migrating-GtkComboBox.html" title="Migrating from GtkOptionMenu and GtkCombo to GtkComboBox and
GtkComboBoxEntry">
<link rel="chapter" href="gtk-migrating-GtkIconView.html" title="Migrating from GnomeIconList to GtkIconView">
<link rel="chapter" href="gtk-migrating-GtkAboutDialog.html" title="Migrating from GnomeAbout to GtkAboutDialog">
<link rel="chapter" href="gtk-migrating-GtkColorButton.html" title="Migrating from GnomeColorPicker to GtkColorButton">
<link rel="chapter" href="gtk-migrating-GtkAssistant.html" title="Migrating from GnomeDruid to GtkAssistant">
<link rel="chapter" href="gtk-migrating-GtkRecentChooser.html" title="Migrating from EggRecent to GtkRecentChooser">
<link rel="chapter" href="gtk-migrating-GtkLinkButton.html" title="Migrating from GnomeHRef to GtkLinkButton">
<link rel="part" href="pt05.html" title="Part V. GTK+ Tools">
<link rel="glossary" href="glossary.html" title="Glossary">
<link rel="index" href="ix01.html" title="Index">
<link rel="index" href="ix02.html" title="Index of deprecated symbols">
<link rel="index" href="ix03.html" title="Index of new symbols in 2.2">
<link rel="index" href="ix04.html" title="Index of new symbols in 2.4">
<link rel="index" href="ix05.html" title="Index of new symbols in 2.6">
<link rel="index" href="ix06.html" title="Index of new symbols in 2.8">
<link rel="index" href="ix07.html" title="Index of new symbols in 2.10">
</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-update-icon-cache.html"><img src="left.png" width="24" height="24" border="0" alt="Prev"></a></td>
<td> </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="ix01.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
</tr></table>
<div class="glossary">
<div class="titlepage"><div><div><h2 class="title">
<a name="glossary"></a>Glossary</h2></div></div></div>
<dl>
<dt>
<a name="allocation"></a>allocation</dt>
<dd>
<p>
The final size of a <a href="glossary.html#widget"><em class="glossterm">widget</em></a> within its <a href="glossary.html#parent"><em class="glossterm">parent</em></a>. For example, a widget
may request a minimum size of 20×20 pixels, but its
parent may decide to allocate 50×20 pixels for it
instead.
</p>
<p>See Also
<a href="glossary.html#requisition"><em class="glossterm">requisition</em></a>
.</p>
</dd>
<dt>
<a name="bin"></a>bin</dt>
<dd>
<p>
A <a href="glossary.html#container"><em class="glossterm">container</em></a> that
can hold at most one child widget. The base class for bins is
<a href="GtkBin.html" title="GtkBin"><span class="type">GtkBin</span></a>.
</p>
<p>See Also
<a href="glossary.html#container"><em class="glossterm">container</em></a>
.</p>
</dd>
<dt>
<a name="child"></a>child</dt>
<dd><p>
A <a href="glossary.html#container"><em class="glossterm">container's</em></a> child
is a <a href="glossary.html#widget"><em class="glossterm">widget</em></a> contained
inside it.
</p></dd>
<dt>
<a name="column"></a>column</dt>
<dd>
<p>
GTK+ contains several widgets which display data in columns,
e.g. the <a href="GtkTreeView.html" title="GtkTreeView"><span class="type">GtkTreeView</span></a>.
These <a href="glossary.html#view-column"><em class="glossterm">view columns</em></a> in
the tree view are represented by <a href="GtkTreeViewColumn.html" title="GtkTreeViewColumn"><span class="type">GtkTreeViewColumn</span></a>
objects inside GTK+. They should not be confused with
<a href="glossary.html#model-column"><em class="glossterm">model columns</em></a> which
are used to organize the data in tree models.
</p>
<p>See Also model-view widget.</p>
</dd>
<dt>
<a name="container"></a>container</dt>
<dd>
<p>
A <a href="glossary.html#widget"><em class="glossterm">widget</em></a> that contains
other widgets; in that case, the container is the
<span class="emphasis"><em>parent</em></span> of the <span class="emphasis"><em>child</em></span>
widgets. Some containers don't draw anything on their own,
but rather just organize their children's <a href="glossary.html#geometry"><em class="glossterm">geometry</em></a>; for example, <a href="GtkVBox.html" title="GtkVBox"><span class="type">GtkVBox</span></a> lays out
its children vertically without painting anything on its own. Other
containers include decorative elements; for example, <a href="GtkFrame.html" title="GtkFrame"><span class="type">GtkFrame</span></a> contains
the frame's child and a label in addition to the shaded frame it draws.
The base class for containers is <a href="GtkContainer.html" title="GtkContainer"><span class="type">GtkContainer</span></a>.
</p>
<p>See Also
<a href="glossary.html#container"><em class="glossterm">widget</em></a>
<a href="glossary.html#container"><em class="glossterm">geometry</em></a>
.</p>
</dd>
<dt>
<a name="display"></a>display</dt>
<dd><p>
GDK inherited the concept of display from the X window system,
which considers a display to be the combination
of a keyboard, a pointing device and one or more
<a href="glossary.html#screen"><em class="glossterm">screens</em></a>.
Applications open a display to show windows and interact with the user.
In GDK, a display is represented by a <a
href="../gdk/GdkDisplay.html"
><span class="type">GdkDisplay</span></a>.
</p></dd>
<dt>
<a name="event"></a>event</dt>
<dd><p>
Events are the way in which GDK informs GTK+ about external events
like pointer motion, button clicks, key presses, etc.
</p></dd>
<dt>
<a name="geometry"></a>geometry</dt>
<dd><p>
A <a href="glossary.html#widget"><em class="glossterm">widget's</em></a> position
and size. Within its parent, this is called the widget's
<a href="glossary.html#allocation"><em class="glossterm">allocation</em></a>.
</p></dd>
<dt>
<a name="mapping"></a>mapping</dt>
<dd>
<p>
This is the step in a <a href="glossary.html#widget"><em class="glossterm">widget's</em></a> life cycle where it
actually shows the GdkWindows it created when it was
<a href="glossary.html#realization"><em class="glossterm">realized</em></a>. When a
widget is mapped, it must turn on its
<a href="GtkWidget.html#GTK-MAPPED:CAPS"><code class="literal">GTK_MAPPED</code></a> <a href="GtkWidget.html#GtkWidgetFlags">flag</a>.
</p>
<p>
Note that due to the asynchronous nature of the X window
system, a widget's window may not appear on the screen
immediatly after one calls <a
href="../gdk/gdk-Windows.html#gdk-window-show"
><code class="function">gdk_window_show()</code></a>:
you must wait for the corresponding map <a href="glossary.html#event"><em class="glossterm">event</em></a> to be received. You can do
this with the <a href="GtkWidget.html#GtkWidget-map-event"><code class="methodname">GtkWidget::map-event</code>
signal</a>.
</p>
</dd>
<dt>
<a name="model-column"></a>model column</dt>
<dd>
<p>
A column in a tree model, holding data of a certain type.
The types which can be stored in the columns of a model
have to be specified when the model is constructed, see
e.g. <a href="GtkListStore.html#gtk-list-store-new"><code class="function">gtk_list_store_new()</code></a>.
</p>
<p>See Also
<a href="glossary.html#view-column"><em class="glossterm">view column</em></a>
.</p>
</dd>
<dt>
<a name="model-view"></a>model-view widget</dt>
<dd>
<p>
These widgets follow the well-known model-view pattern, which separates
the data (the model) to be displayed from the component which does the
actual visualization (the view). Examples of this pattern in GTK+ are
the <a href="GtkTreeView.html" title="GtkTreeView"><span class="type">GtkTreeView</span></a>/<a href="GtkTreeModel.html" title="GtkTreeModel"><span class="type">GtkTreeModel</span></a> and <a href="GtkTextView.html" title="GtkTextView"><span class="type">GtkTextView</span></a>/<a href="GtkTextBuffer.html" title="GtkTextBuffer"><span class="type">GtkTextBuffer</span></a>
</p>
<p>
One important advantage of this pattern is that it is possible to
display the same model in multiple views; another one that the
separation of the model allows a great deal of flexibility, as
demonstrated by e.g. <a href="GtkTreeModelSort.html" title="GtkTreeModelSort"><span class="type">GtkTreeModelSort</span></a> or <a href="GtkTreeModelFilter.html" title="GtkTreeModelFilter"><span class="type">GtkTreeModelFilter</span></a>.
</p>
</dd>
<dt>
<a name="no-window"></a>no-window widget</dt>
<dd><p>
A widget that does not have a GdkWindow of its own on which to
draw its contents, but rather shares its <a href="glossary.html#parent"><em class="glossterm">parent's</em></a>. Such a widget has the
<a href="GtkWidget.html#GTK-NO-WINDOW:CAPS"><code class="literal">GTK_NO_WINDOW</code></a> <a href="GtkWidget.html#GtkWidgetFlags">flag</a> set, and
can be tested with the <a href="GtkWidget.html#GTK-WIDGET-NO-WINDOW:CAPS"><code class="function">GTK_WIDGET_NO_WINDOW()</code></a> macro.
</p></dd>
<dt>
<a name="parent"></a>parent</dt>
<dd><p>
A <a href="glossary.html#widget"><em class="glossterm">widget's</em></a> parent is
the <a href="glossary.html#container"><em class="glossterm">container</em></a>
inside which it resides.
</p></dd>
<dt>
<a name="realization"></a>realization</dt>
<dd>
<p>
This is the step in a <a href="glossary.html#widget"><em class="glossterm">widget's</em></a> life cycle where it
creates its own GdkWindow, or otherwise associates itself with
its <a href="glossary.html#parent"><em class="glossterm">parent's</em></a>
GdkWindow. If the widget has its own window, then it must
also attach a <a href="glossary.html#style"><em class="glossterm">style</em></a> to
it. A widget becomes unrealized by destroying its associated
GdkWindow. When a widget is realized, it must turn on its
<a href="GtkWidget.html#GTK-REALIZED:CAPS"><code class="literal">GTK_REALIZED</code></a> <a href="GtkWidget.html#GtkWidgetFlags">flag</a>.
</p>
<p>
Widgets that don't own the GdkWindow on which they draw are
called <a href="glossary.html#no-window"><em class="glossterm">no-window widgets</em></a>.
This can be tested with the <a href="GtkWidget.html#GTK-WIDGET-NO-WINDOW:CAPS"><code class="function">GTK_WIDGET_NO_WINDOW()</code></a> macro. Normally,
these widgets draw on their parent's GdkWindow.
</p>
<p>
Note that when a widget creates a window in its <code class="methodname">::<GTKDOCLINK HREF="realize"><code class="function">realize()</code></code></GTKDOCLINK>
handler, it does not actually show the window. That is, the
window's structure is just created in memory. The widget
actually shows the window when it gets <a href="glossary.html#mapping"><em class="glossterm">mapped</em></a>.
</p>
</dd>
<dt>
<a name="requisition"></a>requisition</dt>
<dd>
<p>
The size requisition of a <a href="glossary.html#widget"><em class="glossterm">widget</em></a> is the minimum amount of
space it requests from its <a href="glossary.html#parent"><em class="glossterm">parent</em></a>. Once the parent computes
the widget's final size, it gives it its <a href="glossary.html#allocation"><em class="glossterm">size allocation</em></a>.
</p>
<p>See Also
<a href="glossary.html#allocation"><em class="glossterm">allocation</em></a>
.</p>
</dd>
<dt>
<a name="screen"></a>screen</dt>
<dd>
<p>
GDK inherited the concept of screen from the X window system,
which considers a screen to be a rectangular area, on which
applications may place their windows. Screens under X may have
quite dissimilar <a href="glossary.html#visual"><em class="glossterm">visuals</em></a>.
Each screen can stretch across multiple physical monitors.
</p>
<p>
In GDK, screens are represented by <a
href="../gdk/GdkScreen.html"
><span class="type">GdkScreen</span></a> objects.
</p>
</dd>
<dt>
<a name="style"></a>style</dt>
<dd><p>
A style encapsulates what GTK+ needs to know in order to draw
a widget. Styles can be modified with
<a href="gtk-Resource-Files.html" title="Resource Files">resource files</a>.
</p></dd>
<dt>
<a name="toplevel"></a>toplevel</dt>
<dd>
<p>
A <a href="glossary.html#widget"><em class="glossterm">widget</em></a> that does not
require a <a href="glossary.html#parent"><em class="glossterm">parent</em></a> container.
The only toplevel widgets in GTK+ are <a href="GtkWindow.html" title="GtkWindow"><span class="type">GtkWindow</span></a> and widgets derived from it.
</p>
<p>See Also
<a href="glossary.html#container"><em class="glossterm">container</em></a>
.</p>
</dd>
<dt>
<a name="unmap"></a>unmap</dt>
<dd><p>See <a href="glossary.html#mapping"><em class="glossterm">mapping</em></a>.</p></dd>
<dt>
<a name="unrealize"></a>unrealize</dt>
<dd><p>See <a href="glossary.html#realization"><em class="glossterm">realization</em></a>.</p></dd>
<dt>
<a name="view-column"></a>view column</dt>
<dd>
<p>
A displayed column in a tree view, represented by a
<a href="GtkTreeViewColumn.html" title="GtkTreeViewColumn"><span class="type">GtkTreeViewColumn</span></a> object.
</p>
<p>See Also
<a href="glossary.html#model-column"><em class="glossterm">model column</em></a>
.</p>
</dd>
<dt>
<a name="visual"></a>visual</dt>
<dd>
<p>
A visual describes how color information is stored in pixels.
A <a href="glossary.html#screen"><em class="glossterm">screen</em></a> may support
multiple visuals. On modern hardware, the most common visuals
are truecolor visuals, which store a fixed number of bits
(typically 8) for the red, green and blue components of a color.
</p>
<p>
On ancient hardware, one may still meet indexed visuals, which
store color information as an index into a color map, or even
monochrome visuals.
</p>
</dd>
<dt>
<a name="widget"></a>widget</dt>
<dd>
<p>
A control in a graphical user interface. Widgets can draw
themselves and process events from the mouse and keyboard.
Widget types include buttons, menus, text entry lines, and
lists. Widgets can be arranged into <a href="glossary.html#container"><em class="glossterm">containers</em></a>, and these take
care of assigning the <a href="glossary.html#geometry"><em class="glossterm">geometry</em></a> of the widgets: every
widget thus has a parent except those widgets which are
<a href="glossary.html#toplevel"><em class="glossterm">toplevels</em></a>. The base
class for widgets is <a href="GtkWidget.html" title="GtkWidget"><span class="type">GtkWidget</span></a>.
</p>
<p>See Also
<a href="glossary.html#container"><em class="glossterm">container</em></a>
.</p>
</dd>
</dl>
</div>
</body>
</html>