RubyGems - gdk3 - Versions diffs - 2.2.5-x86-mingw32 → 3.0.0-x86-mingw32 - Mend

gdk3 2.2.5-x86-mingw32 → 3.0.0-x86-mingw32

Files changed (796) hide show

data/vendor/local/share/gtk-doc/html/gtk3/broadwayd.html CHANGED Viewed

@@ -2,13 +2,13 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<title>GTK+ 3 Reference Manual: broadwayd</title>
+<title>broadwayd: GTK+ 3 Reference Manual</title>
 <meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
 <link rel="home" href="index.html" title="GTK+ 3 Reference Manual">
 <link rel="up" href="pt06.html" title="Part VI. GTK+ Tools">
 <link rel="prev" href="gtk-launch.html" title="gtk-launch">
 <link rel="next" href="platform-support.html" title="Part VII. GTK+ Platform Support">
-<meta name="generator" content="GTK-Doc V1.21.1 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.24.1 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -33,7 +33,7 @@
 <div class="cmdsynopsis"><p><code class="command">broadwayd</code>  [--port <em class="replaceable"><code>PORT</code></em>] [--address <em class="replaceable"><code>ADDRESS</code></em>] [--unixsocket <em class="replaceable"><code>ADDRESS</code></em>] [<em class="replaceable"><code>:DISPLAY</code></em>]</p></div>
 </div>
 <div class="refsect1">
-<a name="id-1.7.9.5"></a><h2>Description</h2>
+<a name="id-1.7.10.5"></a><h2>Description</h2>
 <p>
 <span class="command"><strong>broadwayd</strong></span> is a display server for the Broadway
 GDK backend. It allows multiple GTK+ applications to display their
@@ -69,7 +69,7 @@ openssl passwd -1  &gt; ~/.config/broadway.passwd
 </p>
 </div>
 <div class="refsect1">
-<a name="id-1.7.9.6"></a><h2>Options</h2>
+<a name="id-1.7.10.6"></a><h2>Options</h2>
 <div class="variablelist"><table border="0" class="variablelist">
 <colgroup>
 <col align="left" valign="top">
@@ -100,7 +100,6 @@ openssl passwd -1  &gt; ~/.config/broadway.passwd
 </div>
 </div>
 <div class="footer">
-<hr>
-          Generated by GTK-Doc V1.21.1</div>
+<hr>Generated by GTK-Doc V1.24.1</div>
 </body>
 </html>

data/vendor/local/share/gtk-doc/html/gtk3/ch01s02.html CHANGED Viewed

@@ -2,13 +2,13 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<title>GTK+ 3 Reference Manual: Packing</title>
+<title>Packing: GTK+ 3 Reference Manual</title>
 <meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
 <link rel="home" href="index.html" title="GTK+ 3 Reference Manual">
 <link rel="up" href="gtk-getting-started.html" title="Getting Started with GTK+">
 <link rel="prev" href="gtk-getting-started.html" title="Getting Started with GTK+">
-<link rel="next" href="ch01s03.html" title="Drawing">
-<meta name="generator" content="GTK-Doc V1.21.1 (XML mode)">
+<link rel="next" href="ch01s03.html" title="Building user interfaces">
+<meta name="generator" content="GTK-Doc V1.24.1 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -21,11 +21,10 @@
 </tr></table>
 <div class="section">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id-1.2.3.4"></a>Packing</h2></div></div></div>
+<a name="id-1.2.3.10"></a>Packing</h2></div></div></div>
 <p>When creating an application, you'll want to put more than one widget
-    inside a window. Our first helloworld example only used one widget so we
-    could simply use a <a class="link" href="GtkContainer.html#gtk-container-add" title="gtk_container_add ()"><code class="function">gtk_container_add()</code></a> call to "pack" the widget into the
-    window. But when you want to put more than one widget into a window, it
+    inside a window.
+    When you want to put more than one widget into a window, it
     it becomes important to control how each widget is positioned and sized.
     This is where packing comes in.</p>
 <p>GTK+ comes with a large variety of <em class="firstterm">layout containers</em>
@@ -47,23 +46,17 @@ print_hello (GtkWidget *widget,
   g_print ("Hello World\n");
 }
-int
-main (int   argc,
-      char *argv[])
+static void
+activate (GtkApplication *app,
+          gpointer        user_data)
 {
   GtkWidget *window;
   GtkWidget *grid;
   GtkWidget *button;
-  /* This is called in all GTK applications. Arguments are parsed
-   * from the command line and are returned to the application.
-   */
-  gtk_init (&amp;argc, &amp;argv);
   /* create a new window, and set its title */
-  window = gtk_window_new (GTK_WINDOW_TOPLEVEL);
-  gtk_window_set_title (GTK_WINDOW (window), "Grid");
-  g_signal_connect (window, "destroy", G_CALLBACK (gtk_main_quit), NULL);
+  window = gtk_application_window_new (app);
+  gtk_window_set_title (GTK_WINDOW (window), "Window");
   gtk_container_set_border_width (GTK_CONTAINER (window), 10);
   /* Here we construct the container that is going pack our buttons */
@@ -89,7 +82,7 @@ main (int   argc,
   gtk_grid_attach (GTK_GRID (grid), button, 1, 0, 1, 1);
   button = gtk_button_new_with_label ("Quit");
-  g_signal_connect (button, "clicked", G_CALLBACK (gtk_main_quit), NULL);
+  g_signal_connect_swapped (button, "clicked", G_CALLBACK (gtk_widget_destroy), window);
   /* Place the Quit button in the grid cell (0, 1), and make it
    * span 2 columns.
@@ -103,13 +96,21 @@ main (int   argc,
    */
   gtk_widget_show_all (window);
-  /* All GTK applications must have a gtk_main(). Control ends here
-   * and waits for an event to occur (like a key press or a mouse event),
-   * until gtk_main_quit() is called.
-   */
-  gtk_main ();
+}
+int
+main (int    argc,
+      char **argv)
+{
+  GtkApplication *app;
+  int status;
+  app = gtk_application_new ("org.gtk.example", G_APPLICATION_FLAGS_NONE);
+  g_signal_connect (app, "activate", G_CALLBACK (activate), NULL);
+  status = g_application_run (G_APPLICATION (app), argc, argv);
+  g_object_unref (app);
-  return 0;
+  return status;
 }
 </pre>
 </div>
@@ -124,7 +125,6 @@ main (int   argc,
     </p>
 </div>
 <div class="footer">
-<hr>
-          Generated by GTK-Doc V1.21.1</div>
+<hr>Generated by GTK-Doc V1.24.1</div>
 </body>
 </html>

data/vendor/local/share/gtk-doc/html/gtk3/ch01s03.html CHANGED Viewed

@@ -2,13 +2,13 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<title>GTK+ 3 Reference Manual: Drawing</title>
+<title>Building user interfaces: GTK+ 3 Reference Manual</title>
 <meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
 <link rel="home" href="index.html" title="GTK+ 3 Reference Manual">
 <link rel="up" href="gtk-getting-started.html" title="Getting Started with GTK+">
 <link rel="prev" href="ch01s02.html" title="Packing">
-<link rel="next" href="ch01s04.html" title="Building user interfaces">
-<meta name="generator" content="GTK-Doc V1.21.1 (XML mode)">
+<link rel="next" href="ch01s04.html" title="Building applications">
+<meta name="generator" content="GTK-Doc V1.24.1 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -21,228 +21,136 @@
 </tr></table>
 <div class="section">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id-1.2.3.5"></a>Drawing</h2></div></div></div>
-<p>Many widgets, like buttons, do all their drawing themselves. You
-    just tell them the label you want to see, and they figure out what font
-    to use, draw the button outline and focus rectangle, etc. Sometimes, it
-    is necessary to do some custom drawing. In that case, a <a class="link" href="GtkDrawingArea.html" title="GtkDrawingArea"><span class="type">GtkDrawingArea</span></a>
-    might be the right widget to use. It offers a canvas on which you can
-    draw by connecting to the <a class="link" href="GtkWidget.html#GtkWidget-draw" title="The “draw” signal"><span class="type">“draw”</span></a> signal.
-    </p>
-<p>The contents of a widget often need to be partially or fully redrawn,
-    e.g. when another window is moved and uncovers part of the widget, or
-    when tie window containing it is resized. It is also possible to explicitly
-    cause part or all of the widget to be redrawn, by calling
-    <a class="link" href="GtkWidget.html#gtk-widget-queue-draw" title="gtk_widget_queue_draw ()"><code class="function">gtk_widget_queue_draw()</code></a> or its variants. GTK+ takes care of most of the
-    details by providing a ready-to-use cairo context to the ::draw signal
-    handler.</p>
-<p>The following example shows a ::draw signal handler. It is a bit
-    more complicated than the previous examples, since it also demonstrates
-    input event handling by means of ::button-press and ::motion-notify
-    handlers.</p>
-<div class="informalfigure"><div class="mediaobject"><img src="drawing.png"></div></div>
+<a name="id-1.2.3.11"></a>Building user interfaces</h2></div></div></div>
+<p>When construcing a more complicated user interface, with dozens
+    or hundreds of widgets, doing all the setup work in C code is
+    cumbersome, and making changes becomes next to impossible.</p>
+<p>Thankfully, GTK+ supports the separation of user interface
+    layout from your business logic, by using UI descriptions in an
+    XML format that can be parsed by the <a class="link" href="GtkBuilder.html" title="GtkBuilder"><span class="type">GtkBuilder</span></a> class.</p>
 <div class="example">
-<a name="gtk-getting-started-drawing"></a><p class="title"><b>Example 3. Drawing in response to input</b></p>
+<a name="id-1.2.3.11.4"></a><p class="title"><b>Example 3. Packing buttons with GtkBuilder</b></p>
 <div class="example-contents">
-<p>Create a new file with the following content named example-3.c.</p>
+<p>Create a new file with the following content named example-4.c.</p>
 <pre class="programlisting">#include &lt;gtk/gtk.h&gt;
-/* Surface to store current scribbles */
-static cairo_surface_t *surface = NULL;
 static void
-clear_surface (void)
-{
-  cairo_t *cr;
-  cr = cairo_create (surface);
-  cairo_set_source_rgb (cr, 1, 1, 1);
-  cairo_paint (cr);
-  cairo_destroy (cr);
-}
-/* Create a new surface of the appropriate size to store our scribbles */
-static gboolean
-configure_event_cb (GtkWidget         *widget,
-                    GdkEventConfigure *event,
-                    gpointer           data)
+print_hello (GtkWidget *widget,
+             gpointer   data)
 {
-  if (surface)
-    cairo_surface_destroy (surface);
-  surface = gdk_window_create_similar_surface (gtk_widget_get_window (widget),
-                                               CAIRO_CONTENT_COLOR,
-                                               gtk_widget_get_allocated_width (widget),
-                                               gtk_widget_get_allocated_height (widget));
-  /* Initialize the surface to white */
-  clear_surface ();
-  /* We've handled the configure event, no need for further processing. */
-  return TRUE;
-}
-/* Redraw the screen from the surface. Note that the ::draw
- * signal receives a ready-to-be-used cairo_t that is already
- * clipped to only draw the exposed areas of the widget
- */
-static gboolean
-draw_cb (GtkWidget *widget,
-         cairo_t   *cr,
-         gpointer   data)
-{
-  cairo_set_source_surface (cr, surface, 0, 0);
-  cairo_paint (cr);
-  return FALSE;
-}
-/* Draw a rectangle on the surface at the given position */
-static void
-draw_brush (GtkWidget *widget,
-            gdouble    x,
-            gdouble    y)
-{
-  cairo_t *cr;
-  /* Paint to the surface, where we store our state */
-  cr = cairo_create (surface);
-  cairo_rectangle (cr, x - 3, y - 3, 6, 6);
-  cairo_fill (cr);
-  cairo_destroy (cr);
-  /* Now invalidate the affected region of the drawing area. */
-  gtk_widget_queue_draw_area (widget, x - 3, y - 3, 6, 6);
-}
-/* Handle button press events by either drawing a rectangle
- * or clearing the surface, depending on which button was pressed.
- * The ::button-press signal handler receives a GdkEventButton
- * struct which contains this information.
- */
-static gboolean
-button_press_event_cb (GtkWidget      *widget,
-                       GdkEventButton *event,
-                       gpointer        data)
-{
-  /* paranoia check, in case we haven't gotten a configure event */
-  if (surface == NULL)
-    return FALSE;
-  if (event-&gt;button == GDK_BUTTON_PRIMARY)
-    {
-      draw_brush (widget, event-&gt;x, event-&gt;y);
-    }
-  else if (event-&gt;button == GDK_BUTTON_SECONDARY)
-    {
-      clear_surface ();
-      gtk_widget_queue_draw (widget);
-    }
-  /* We've handled the event, stop processing */
-  return TRUE;
-}
-/* Handle motion events by continuing to draw if button 1 is
- * still held down. The ::motion-notify signal handler receives
- * a GdkEventMotion struct which contains this information.
- */
-static gboolean
-motion_notify_event_cb (GtkWidget      *widget,
-                        GdkEventMotion *event,
-                        gpointer        data)
-{
-  /* paranoia check, in case we haven't gotten a configure event */
-  if (surface == NULL)
-    return FALSE;
-  if (event-&gt;state &amp; GDK_BUTTON1_MASK)
-    draw_brush (widget, event-&gt;x, event-&gt;y);
-  /* We've handled it, stop processing */
-  return TRUE;
-}
-static void
-close_window (void)
-{
-  if (surface)
-    cairo_surface_destroy (surface);
-  gtk_main_quit ();
+  g_print ("Hello World\n");
 }
 int
 main (int   argc,
       char *argv[])
 {
-  GtkWidget *window;
-  GtkWidget *frame;
-  GtkWidget *da;
+  GtkBuilder *builder;
+  GObject *window;
+  GObject *button;
   gtk_init (&amp;argc, &amp;argv);
-  window = gtk_window_new (GTK_WINDOW_TOPLEVEL);
-  gtk_window_set_title (GTK_WINDOW (window), "Drawing Area");
-  g_signal_connect (window, "destroy", G_CALLBACK (close_window), NULL);
-  gtk_container_set_border_width (GTK_CONTAINER (window), 8);
+  /* Construct a GtkBuilder instance and load our UI description */
+  builder = gtk_builder_new ();
+  gtk_builder_add_from_file (builder, "builder.ui", NULL);
-  frame = gtk_frame_new (NULL);
-  gtk_frame_set_shadow_type (GTK_FRAME (frame), GTK_SHADOW_IN);
-  gtk_container_add (GTK_CONTAINER (window), frame);
+  /* Connect signal handlers to the constructed widgets. */
+  window = gtk_builder_get_object (builder, "window");
+  g_signal_connect (window, "destroy", G_CALLBACK (gtk_main_quit), NULL);
-  da = gtk_drawing_area_new ();
-  /* set a minimum size */
-  gtk_widget_set_size_request (da, 100, 100);
+  button = gtk_builder_get_object (builder, "button1");
+  g_signal_connect (button, "clicked", G_CALLBACK (print_hello), NULL);
-  gtk_container_add (GTK_CONTAINER (frame), da);
+  button = gtk_builder_get_object (builder, "button2");
+  g_signal_connect (button, "clicked", G_CALLBACK (print_hello), NULL);
-  /* Signals used to handle the backing surface */
-  g_signal_connect (da, "draw",
-                    G_CALLBACK (draw_cb), NULL);
-  g_signal_connect (da,"configure-event",
-                    G_CALLBACK (configure_event_cb), NULL);
-  /* Event signals */
-  g_signal_connect (da, "motion-notify-event",
-                    G_CALLBACK (motion_notify_event_cb), NULL);
-  g_signal_connect (da, "button-press-event",
-                    G_CALLBACK (button_press_event_cb), NULL);
-  /* Ask to receive events the drawing area doesn't normally
-   * subscribe to. In particular, we need to ask for the
-   * button press and motion notify events that want to handle.
-   */
-  gtk_widget_set_events (da, gtk_widget_get_events (da)
-                             | GDK_BUTTON_PRESS_MASK
-                             | GDK_POINTER_MOTION_MASK);
-  gtk_widget_show_all (window);
+  button = gtk_builder_get_object (builder, "quit");
+  g_signal_connect (button, "clicked", G_CALLBACK (gtk_main_quit), NULL);
   gtk_main ();
   return 0;
 }
 </pre>
+<p>Create a new file with the following content named builder.ui.</p>
+<pre class="programlisting">&lt;interface&gt;
+  &lt;object id="window" class="GtkWindow"&gt;
+    &lt;property name="visible"&gt;True&lt;/property&gt;
+    &lt;property name="title"&gt;Grid&lt;/property&gt;
+    &lt;property name="border-width"&gt;10&lt;/property&gt;
+    &lt;child&gt;
+      &lt;object id="grid" class="GtkGrid"&gt;
+        &lt;property name="visible"&gt;True&lt;/property&gt;
+        &lt;child&gt;
+          &lt;object id="button1" class="GtkButton"&gt;
+            &lt;property name="visible"&gt;True&lt;/property&gt;
+            &lt;property name="label"&gt;Button 1&lt;/property&gt;
+          &lt;/object&gt;
+          &lt;packing&gt;
+            &lt;property name="left-attach"&gt;0&lt;/property&gt;
+            &lt;property name="top-attach"&gt;0&lt;/property&gt;
+          &lt;/packing&gt;
+        &lt;/child&gt;
+        &lt;child&gt;
+          &lt;object id="button2" class="GtkButton"&gt;
+            &lt;property name="visible"&gt;True&lt;/property&gt;
+            &lt;property name="label"&gt;Button 2&lt;/property&gt;
+          &lt;/object&gt;
+          &lt;packing&gt;
+            &lt;property name="left-attach"&gt;1&lt;/property&gt;
+            &lt;property name="top-attach"&gt;0&lt;/property&gt;
+          &lt;/packing&gt;
+        &lt;/child&gt;
+        &lt;child&gt;
+          &lt;object id="quit" class="GtkButton"&gt;
+            &lt;property name="visible"&gt;True&lt;/property&gt;
+            &lt;property name="label"&gt;Quit&lt;/property&gt;
+          &lt;/object&gt;
+          &lt;packing&gt;
+            &lt;property name="left-attach"&gt;0&lt;/property&gt;
+            &lt;property name="top-attach"&gt;1&lt;/property&gt;
+            &lt;property name="width"&gt;2&lt;/property&gt;
+          &lt;/packing&gt;
+        &lt;/child&gt;
+      &lt;/object&gt;
+      &lt;packing&gt;
+      &lt;/packing&gt;
+    &lt;/child&gt;
+  &lt;/object&gt;
+&lt;/interface&gt;
+</pre>
 </div>
 </div>
 <br class="example-break"><p>
       You can compile the program above with GCC using:
       </p>
 <div class="literallayout"><p><br>
-        <code class="literal">gcc `pkg-config --cflags gtk+-3.0` -o example-3 example-3.c `pkg-config --libs gtk+-3.0`</code><br>
+        <code class="literal">gcc `pkg-config --cflags gtk+-3.0` -o example-4 example-4.c `pkg-config --libs gtk+-3.0`</code><br>
       </p></div>
 <p>
     </p>
+<p>Note that GtkBuilder can also be used to construct objects
+    that are not widgets, such as tree models, adjustments, etc.
+    That is the reason the method we use here is called
+    <a class="link" href="GtkBuilder.html#gtk-builder-get-object" title="gtk_builder_get_object ()"><code class="function">gtk_builder_get_object()</code></a> and returns a GObject* instead of a
+    GtkWidget*.</p>
+<p>Normally, you would pass a full path to
+    <a class="link" href="GtkBuilder.html#gtk-builder-add-from-file" title="gtk_builder_add_from_file ()"><code class="function">gtk_builder_add_from_file()</code></a> to make the execution of your program
+    independent of the current directory. A common location to install
+    UI descriptions and similar data is
+    <code class="filename">/usr/share/<em class="replaceable"><code>appname</code></em></code>.
+    </p>
+<p>It is also possible to embed the UI description in the source
+    code as a string and use <a class="link" href="GtkBuilder.html#gtk-builder-add-from-string" title="gtk_builder_add_from_string ()"><code class="function">gtk_builder_add_from_string()</code></a> to load it.
+    But keeping the UI description in a separate file has several
+    advantages: It is then possible to make minor adjustments to the UI
+    without recompiling your program, and, more importantly, graphical
+    UI editors such as <a class="ulink" href="http://glade.gnome.org" target="_top">glade</a>
+    can load the file and allow you to create and modify your UI by
+    point-and-click.</p>
 </div>
 <div class="footer">
-<hr>
-          Generated by GTK-Doc V1.21.1</div>
+<hr>Generated by GTK-Doc V1.24.1</div>
 </body>
 </html>