gtk2/gtk/ui/gtkdialog.ui

<?xml version="1.0" encoding="UTF-8"?>
<interface domain="gtk40">
  <template class="GtkDialog" parent="GtkWindow">
    <property name="type-hint">dialog</property>
    <child type="titlebar">
      <object class="GtkHeaderBar" id="headerbar">
        <property name="show-title-buttons">1</property>
        <property name="has-subtitle">false</property>
      </object>
    </child>
    <child>
      <object class="GtkBox">
        <property name="orientation">vertical</property>
        <style>
          <class name="dialog-vbox"/>
        </style>
        <child>
          <object class="GtkBox" id="content_area"/>
        </child>
        <child>
          <object class="GtkBox" id="action_box">
            <style>
              <class name="dialog-action-box"/>
            </style>
            <child>
              <object class="GtkBox" id="action_area">
                <property name="hexpand">1</property>
                <property name="halign">end</property>
                <style>
                  <class name="dialog-action-area"/>
                </style>
              </object>
            </child>
          </object>
        </child>
      </object>
    </child>
  </template>
</interface>
Update GtkGrid definitions in GtkBuilder files Convert packing properties to layout ones. 2019-04-04 23:08:18 +00:00			`<?xml version="1.0" encoding="UTF-8"?>`
Use the right gettext domain Most of our .ui files were still using the gtk30 domain, despite the library having switched to gtk40. Fix this. 2017-08-05 22:17:29 +00:00			`<interface domain="gtk40">`
GtkDialog: Define children with a GtkBuilder template As the first composite widget in GTK+, this patch also adds some Makefile mechanics to list the ui files as dependencies of the global GTK+ resources, and adds the initial test case where composite classes should be tested. 2013-03-21 08:54:16 +00:00			`<template class="GtkDialog" parent="GtkWindow">`
Simplify our templates This is applying the new property name simplification. 2016-05-06 17:45:46 +00:00			`<property name="type-hint">dialog</property>`
dialog: Add a headerbar This change makes it possible for GtkDialog to pack its action widgets into a header bar, instead of the traditional action area. This change is controlled by the use-header-bar construct-only property. https://bugzilla.gnome.org/show_bug.cgi?id=720059 2013-12-08 18:15:40 +00:00			`<child type="titlebar">`
			`<object class="GtkHeaderBar" id="headerbar">`
Fix fallout from the show-close-button rename I had overlooked ui files. We should really validate those during build. 2017-12-08 16:29:14 +00:00			`<property name="show-title-buttons">1</property>`
dialog: Use default decoration for non-custom headerbars There are two ways GTK can add a headerbar to a dialog: - the dialog is constructed with the :use-header-bar property - all windows should use client-side decorations In the first case, the headerbar is added by GtkDialog with no dedicated style class, and in the latter by GtkWindow with the "default-decoration" style. As a result, dialogs with plain titlebars can end up with clearly distinct and inconsistent styles. To address this, allow headerbars to track whether they should use the "default-decoration" style and enable it for dialogs. https://gitlab.gnome.org/GNOME/gtk/merge_requests/836 2019-05-12 09:58:22 +00:00			`<property name="has-subtitle">false</property>`
dialog: Add a headerbar This change makes it possible for GtkDialog to pack its action widgets into a header bar, instead of the traditional action area. This change is controlled by the use-header-bar construct-only property. https://bugzilla.gnome.org/show_bug.cgi?id=720059 2013-12-08 18:15:40 +00:00			`</object>`
			`</child>`
GtkDialog: Define children with a GtkBuilder template As the first composite widget in GTK+, this patch also adds some Makefile mechanics to list the ui files as dependencies of the global GTK+ resources, and adds the initial test case where composite classes should be tested. 2013-03-21 08:54:16 +00:00			`<child>`
dialog: Expose the content area as a separate GtkBox child This way, the "vbox" internal child does not contain anything by default. It previously did contain "internal" widgetry like the action area. 2018-12-26 08:00:08 +00:00			`<object class="GtkBox">`
GtkDialog: Define children with a GtkBuilder template As the first composite widget in GTK+, this patch also adds some Makefile mechanics to list the ui files as dependencies of the global GTK+ resources, and adds the initial test case where composite classes should be tested. 2013-03-21 08:54:16 +00:00			`<property name="orientation">vertical</property>`
dialog: Add style classes These will be used in subsequent commits to better style message dialogs. 2014-01-17 17:39:05 +00:00			`<style>`
			`<class name="dialog-vbox"/>`
			`</style>`
dialog: Expose the content area as a separate GtkBox child This way, the "vbox" internal child does not contain anything by default. It previously did contain "internal" widgetry like the action area. 2018-12-26 08:00:08 +00:00			`<child>`
Update ui files to new stack syntax This conversion was done with the help of gtk4-builder-tool. 2019-02-07 08:23:02 +00:00			`<object class="GtkBox" id="content_area"/>`
dialog: Expose the content area as a separate GtkBox child This way, the "vbox" internal child does not contain anything by default. It previously did contain "internal" widgetry like the action area. 2018-12-26 08:00:08 +00:00			`</child>`
GtkDialog: Define children with a GtkBuilder template As the first composite widget in GTK+, this patch also adds some Makefile mechanics to list the ui files as dependencies of the global GTK+ resources, and adds the initial test case where composite classes should be tested. 2013-03-21 08:54:16 +00:00			`<child>`
dialog: add a box around the action area to use for styling If we want to set style properties that include the area of the border-width part of action_area we need to use a parent box. https://bugzilla.gnome.org/show_bug.cgi?id=722211 2014-04-09 18:30:37 +00:00			`<object class="GtkBox" id="action_box">`
dialog: Add style classes These will be used in subsequent commits to better style message dialogs. 2014-01-17 17:39:05 +00:00			`<style>`
dialog: add a box around the action area to use for styling If we want to set style properties that include the area of the border-width part of action_area we need to use a parent box. https://bugzilla.gnome.org/show_bug.cgi?id=722211 2014-04-09 18:30:37 +00:00			`<class name="dialog-action-box"/>`
dialog: Add style classes These will be used in subsequent commits to better style message dialogs. 2014-01-17 17:39:05 +00:00			`</style>`
dialog: add a box around the action area to use for styling If we want to set style properties that include the area of the border-width part of action_area we need to use a parent box. https://bugzilla.gnome.org/show_bug.cgi?id=722211 2014-04-09 18:30:37 +00:00			`<child>`
Drop GtkButtonBox This widget does not seem worth keeping, and we want to get rid of child properties. 2019-02-04 17:44:55 +00:00			`<object class="GtkBox" id="action_area">`
Run gtk-builder-tool simplify over all templates 2015-09-09 20:50:49 +00:00			`<property name="hexpand">1</property>`
Drop GtkButtonBox This widget does not seem worth keeping, and we want to get rid of child properties. 2019-02-04 17:44:55 +00:00			`<property name="halign">end</property>`
dialog: add a box around the action area to use for styling If we want to set style properties that include the area of the border-width part of action_area we need to use a parent box. https://bugzilla.gnome.org/show_bug.cgi?id=722211 2014-04-09 18:30:37 +00:00			`<style>`
			`<class name="dialog-action-area"/>`
			`</style>`
			`</object>`
			`</child>`
			`</object>`
GtkDialog: Define children with a GtkBuilder template As the first composite widget in GTK+, this patch also adds some Makefile mechanics to list the ui files as dependencies of the global GTK+ resources, and adds the initial test case where composite classes should be tested. 2013-03-21 08:54:16 +00:00			`</child>`
			`</object>`
			`</child>`
			`</template>`
			`</interface>`