@gtkx/react 0.5.2 → 0.6.0

package/dist/generated/jsx.js

@@ -169,28 +169,28 @@ import { createElement } from "react";
  *
  * ```xml
  * <object class="GtkGrid" id="my_grid">
- * <child>
+ * `<child>`
  * <object class="GtkLabel" id="label1">
- * <property name="label">Description</property>
+ * <property name="label">Description`</property>`
  * <layout>
- * <property name="column">0</property>
- * <property name="row">0</property>
- * <property name="row-span">1</property>
- * <property name="column-span">1</property>
+ * <property name="column">0`</property>`
+ * <property name="row">0`</property>`
+ * <property name="row-span">1`</property>`
+ * <property name="column-span">1`</property>`
  * </layout>
- * </object>
- * </child>
- * <child>
+ * `</object>`
+ * `</child>`
+ * `<child>`
  * <object class="GtkEntry" id="description_entry">
  * <layout>
- * <property name="column">1</property>
- * <property name="row">0</property>
- * <property name="row-span">1</property>
- * <property name="column-span">1</property>
+ * <property name="column">1`</property>`
+ * <property name="row">0`</property>`
+ * <property name="row-span">1`</property>`
+ * <property name="column-span">1`</property>`
  * </layout>
- * </object>
- * </child>
- * </object>
+ * `</object>`
+ * `</child>`
+ * `</object>`
  * ```
  *
  * `GtkWidget` allows style information such as style classes to
@@ -202,7 +202,7 @@ import { createElement } from "react";
  * <class name="my-special-button-class"/>
  * <class name="dark-button"/>
  * </style>
- * </object>
+ * `</object>`
  * ```
  *
  * `GtkWidget` allows defining accessibility information, such as properties,
@@ -211,10 +211,10 @@ import { createElement } from "react";
  * ```xml
  * <object class="GtkButton" id="button1">
  * <accessibility>
- * <property name="label">Download</property>
+ * <property name="label">Download`</property>`
  * <relation name="labelled-by">label1</relation>
  * </accessibility>
- * </object>
+ * `</object>`
  * ```
  *
  * ### Building composite widgets from template XML
@@ -230,50 +230,50 @@ import { createElement } from "react";
  * is slightly different from regular [class@Gtk.Builder] XML.
  *
  * Unlike regular interface descriptions, [method@Gtk.WidgetClass.set_template]
- * will expect a `<template>` tag as a direct child of the toplevel
- * `<interface>` tag. The `<template>` tag must specify the “class” attribute
+ * will expect a ``<template>`` tag as a direct child of the toplevel
+ * `<interface>` tag. The ``<template>`` tag must specify the “class” attribute
  * which must be the type name of the widget. Optionally, the “parent”
  * attribute may be specified to specify the direct parent type of the widget
  * type; this is ignored by `GtkBuilder` but can be used by UI design tools to
  * introspect what kind of properties and internal children exist for a given
  * type when the actual type does not exist.
  *
- * The XML which is contained inside the `<template>` tag behaves as if it were
- * added to the `<object>` tag defining the widget itself. You may set properties
- * on a widget by inserting `<property>` tags into the `<template>` tag, and also
- * add `<child>` tags to add children and extend a widget in the normal way you
- * would with `<object>` tags.
+ * The XML which is contained inside the ``<template>`` tag behaves as if it were
+ * added to the ``<object>`` tag defining the widget itself. You may set properties
+ * on a widget by inserting ``<property>`` tags into the ``<template>`` tag, and also
+ * add ``<child>`` tags to add children and extend a widget in the normal way you
+ * would with ``<object>`` tags.
  *
- * Additionally, `<object>` tags can also be added before and after the initial
- * `<template>` tag in the normal way, allowing one to define auxiliary objects
+ * Additionally, ``<object>`` tags can also be added before and after the initial
+ * ``<template>`` tag in the normal way, allowing one to define auxiliary objects
  * which might be referenced by other widgets declared as children of the
- * `<template>` tag.
+ * ``<template>`` tag.
  *
- * Since, unlike the `<object>` tag, the `<template>` tag does not contain an
+ * Since, unlike the ``<object>`` tag, the ``<template>`` tag does not contain an
  * “id” attribute, if you need to refer to the instance of the object itself that
  * the template will create, simply refer to the template class name in an
  * applicable element content.
  *
  * Here is an example of a template definition, which includes an example of
- * this in the `<signal>` tag:
+ * this in the ``<signal>`` tag:
  *
  * ```xml
  * <interface>
  * <template class="FooWidget" parent="GtkBox">
- * <property name="orientation">horizontal</property>
- * <property name="spacing">4</property>
- * <child>
+ * <property name="orientation">horizontal`</property>`
+ * <property name="spacing">4`</property>`
+ * `<child>`
  * <object class="GtkButton" id="hello_button">
- * <property name="label">Hello World</property>
+ * <property name="label">Hello World`</property>`
  * <signal name="clicked" handler="hello_button_clicked" object="FooWidget" swapped="yes"/>
- * </object>
- * </child>
- * <child>
+ * `</object>`
+ * `</child>`
+ * `<child>`
  * <object class="GtkButton" id="goodbye_button">
- * <property name="label">Goodbye World</property>
- * </object>
- * </child>
- * </template>
+ * <property name="label">Goodbye World`</property>`
+ * `</object>`
+ * `</child>`
+ * `</template>`
  * </interface>
  * ```
  *
@@ -408,7 +408,7 @@ export const Widget = "Widget";
  *
  * The `GtkWindow` implementation of the [iface@Gtk.Buildable] interface supports
  * setting a child as the titlebar by specifying “titlebar” as the “type”
- * attribute of a `<child>` element.
+ * attribute of a ``<child>`` element.
  *
  * # Shortcuts and Gestures
  *
@@ -436,7 +436,7 @@ export const Widget = "Widget";
  *
  * ```
  * window.background [.csd / .solid-csd / .ssd] [.maximized / .fullscreen / .tiled]
- * ├── <child>
+ * ├── `<child>`
  * ╰── <titlebar child>.titlebar [.default-decoration]
  * ```
  *
@@ -548,7 +548,7 @@ export const AboutDialog = "AboutDialog";
  *
  * The `GtkActionBar` implementation of the `GtkBuildable` interface supports
  * adding children at the start or end sides by specifying “start” or “end” as
- * the “type” attribute of a `<child>` element, or setting the center widget
+ * the “type” attribute of a ``<child>`` element, or setting the center widget
  * by specifying “center” value.
  *
  * # CSS nodes
@@ -946,7 +946,7 @@ export const CellView = "CellView";
  *
  * The `GtkCenterBox` implementation of the `GtkBuildable` interface
  * supports placing children in the 3 positions by specifying “start”, “center”
- * or “end” as the “type” attribute of a `<child>` element.
+ * or “end” as the “type” attribute of a ``<child>`` element.
  *
  * # CSS nodes
  *
@@ -1323,7 +1323,7 @@ export const ComboBox = "ComboBox";
  * <item translatable="yes" id="home">Home</item>
  * <item translatable="yes" id="subway">Subway</item>
  * </items>
- * </object>
+ * `</object>`
  * ```
  *
  * ## CSS nodes
@@ -1437,7 +1437,7 @@ export const ComboBoxText = "ComboBoxText";
  * to true.
  *
  * `GtkDialog` supports adding action widgets by specifying “action” as
- * the “type” attribute of a `<child>` element. The widget will be added
+ * the “type” attribute of a ``<child>`` element. The widget will be added
  * either to the action area or the headerbar of the dialog, depending
  * on the “use-header-bar” property. The response id has to be associated
  * with the action widget using the `<action-widgets>` element.
@@ -1448,16 +1448,16 @@ export const ComboBoxText = "ComboBoxText";
  * <object class="GtkDialog" id="dialog1">
  * <child type="action">
  * <object class="GtkButton" id="button_cancel"/>
- * </child>
+ * `</child>`
  * <child type="action">
  * <object class="GtkButton" id="button_ok">
- * </object>
- * </child>
+ * `</object>`
+ * `</child>`
  * <action-widgets>
  * <action-widget response="cancel">button_cancel</action-widget>
  * <action-widget response="ok" default="true">button_ok</action-widget>
  * </action-widgets>
- * </object>
+ * `</object>`
  * ```
  *
  * # Accessibility
@@ -1602,9 +1602,9 @@ function DropDownItem(props) {
  * <item translatable="yes">Home</item>
  * <item translatable="yes">Subway</item>
  * </items>
- * </object>
- * </property>
- * </object>
+ * `</object>`
+ * `</property>`
+ * `</object>`
  * ```
  *
  * If a `GtkDropDown` is created in this manner, or with
@@ -1790,7 +1790,7 @@ export const EmojiChooser = "EmojiChooser";
  * <attribute name="weight" value="PANGO_WEIGHT_BOLD"/>
  * <attribute name="background" value="red" start="5" end="10"/>
  * </attributes>
- * </object>
+ * `</object>`
  * ```
  *
  * The start and end attributes specify the range of characters to which the
@@ -1865,11 +1865,11 @@ export const Entry = "Entry";
  * <object class="GtkExpander">
  * <property name="label-widget">
  * <object class="GtkLabel" id="expander-label"/>
- * </property>
+ * `</property>`
  * <property name="child">
  * <object class="GtkEntry" id="expander-content"/>
- * </property>
- * </object>
+ * `</property>`
+ * `</object>`
  * ```
  *
  * # CSS nodes
@@ -1880,7 +1880,7 @@ export const Entry = "Entry";
  * ├── title
  * │   ├── expander
  * │   ╰── <label widget>
- * ╰── <child>
+ * ╰── `<child>`
  * ```
  *
  * `GtkExpander` has a main node `expander-widget`, and subnode `box` containing
@@ -2188,9 +2188,9 @@ export const Fixed = "Fixed";
  * ```
  * flowbox
  * ├── flowboxchild
- * │   ╰── <child>
+ * │   ╰── `<child>`
  * ├── flowboxchild
- * │   ╰── <child>
+ * │   ╰── `<child>`
  * ┊
  * ╰── [rubberband]
  * ```
@@ -2313,11 +2313,11 @@ export const FontDialogButton = "FontDialogButton";
  * <object class="GtkFrame">
  * <property name="label-widget">
  * <object class="GtkLabel" id="frame_label"/>
- * </property>
+ * `</property>`
  * <property name="child">
  * <object class="GtkEntry" id="frame_content"/>
- * </property>
- * </object>
+ * `</property>`
+ * `</object>`
  * ```
  *
  * # CSS nodes
@@ -2325,7 +2325,7 @@ export const FontDialogButton = "FontDialogButton";
  * ```
  * frame
  * ├── <label widget>
- * ╰── <child>
+ * ╰── `<child>`
  * ```
  *
  * `GtkFrame` has a main CSS node with name “frame”, which is used to draw the
@@ -2523,45 +2523,45 @@ export const GraphicsOffload = "GraphicsOffload";
  *
  * ```xml
  * <object class="GtkGrid" id="my_grid">
- * <child>
+ * `<child>`
  * <object class="GtkButton" id="button1">
- * <property name="label">Button 1</property>
+ * <property name="label">Button 1`</property>`
  * <layout>
- * <property name="column">0</property>
- * <property name="row">0</property>
+ * <property name="column">0`</property>`
+ * <property name="row">0`</property>`
  * </layout>
- * </object>
- * </child>
- * <child>
+ * `</object>`
+ * `</child>`
+ * `<child>`
  * <object class="GtkButton" id="button2">
- * <property name="label">Button 2</property>
+ * <property name="label">Button 2`</property>`
  * <layout>
- * <property name="column">1</property>
- * <property name="row">0</property>
+ * <property name="column">1`</property>`
+ * <property name="row">0`</property>`
  * </layout>
- * </object>
- * </child>
- * <child>
+ * `</object>`
+ * `</child>`
+ * `<child>`
  * <object class="GtkButton" id="button3">
- * <property name="label">Button 3</property>
+ * <property name="label">Button 3`</property>`
  * <layout>
- * <property name="column">2</property>
- * <property name="row">0</property>
- * <property name="row-span">2</property>
+ * <property name="column">2`</property>`
+ * <property name="row">0`</property>`
+ * <property name="row-span">2`</property>`
  * </layout>
- * </object>
- * </child>
- * <child>
+ * `</object>`
+ * `</child>`
+ * `<child>`
  * <object class="GtkButton" id="button4">
- * <property name="label">Button 4</property>
+ * <property name="label">Button 4`</property>`
  * <layout>
- * <property name="column">0</property>
- * <property name="row">1</property>
- * <property name="column-span">2</property>
+ * <property name="column">0`</property>`
+ * <property name="row">1`</property>`
+ * <property name="column-span">2`</property>`
  * </layout>
- * </object>
- * </child>
- * </object>
+ * `</object>`
+ * `</child>`
+ * `</object>`
  * ```
  *
  * It organizes the first two buttons side-by-side in one cell each.
@@ -2661,7 +2661,7 @@ export const GridView = {
  *
  * The `GtkHeaderBar` implementation of the `GtkBuildable` interface supports
  * adding children at the start or end sides by specifying “start” or “end” as
- * the “type” attribute of a `<child>` element, or setting the title widget by
+ * the “type” attribute of a ``<child>`` element, or setting the title widget by
  * specifying “title” value.
  *
  * By default the `GtkHeaderBar` uses a `GtkLabel` displaying the title of the
@@ -2672,16 +2672,16 @@ export const GridView = {
  * <object class="GtkHeaderBar">
  * <property name="title-widget">
  * <object class="GtkLabel">
- * <property name="label" translatable="yes">Label</property>
- * <property name="single-line-mode">True</property>
- * <property name="ellipsize">end</property>
- * <property name="width-chars">5</property>
+ * <property name="label" translatable="yes">Label`</property>`
+ * <property name="single-line-mode">True`</property>`
+ * <property name="ellipsize">end`</property>`
+ * <property name="width-chars">5`</property>`
  * <style>
  * <class name="title"/>
  * </style>
- * </object>
- * </property>
- * </object>
+ * `</object>`
+ * `</property>`
+ * `</object>`
  * ```
  *
  * # CSS nodes
@@ -2848,7 +2848,7 @@ export const Image = "Image";
  * (which should be a child of the dialogs @action_area).
  *
  * `GtkInfoBar` supports adding action widgets by specifying “action” as
- * the “type” attribute of a `<child>` element. The widget will be added
+ * the “type” attribute of a ``<child>`` element. The widget will be added
  * either to the action area. The response id has to be associated
  * with the action widget using the `<action-widgets>` element.
  *
@@ -2958,7 +2958,7 @@ export const Inscription = "Inscription";
  * <attribute name="weight" value="PANGO_WEIGHT_BOLD"/>
  * <attribute name="background" value="red" start="5" end="10"/>
  * </attributes>
- * </object>
+ * `</object>`
  * ```
  *
  * The start and end attributes specify the range of characters to which the
@@ -3095,10 +3095,7 @@ export const Inscription = "Inscription";
  * with the [signal@Gtk.Label::activate-link] signal and the
  * [method@Gtk.Label.get_current_uri] function.
  */
-export const Label = {
-    Root: "Label.Root",
-    MnemonicWidget: "Label.MnemonicWidget",
-};
+export const Label = "Label";
 /**
  * Shows a level indicator.
  *
@@ -3318,7 +3315,7 @@ export const ListBase = "ListBase";
  *
  * The `GtkListBox` implementation of the `GtkBuildable` interface supports
  * setting a child as the placeholder by specifying “placeholder” as the “type”
- * attribute of a `<child>` element. See [method@Gtk.ListBox.set_placeholder]
+ * attribute of a ``<child>`` element. See [method@Gtk.ListBox.set_placeholder]
  * for info.
  *
  * # Shortcuts and Gestures
@@ -3671,30 +3668,30 @@ export const MessageDialog = "MessageDialog";
  *
  * The `GtkNotebook` implementation of the `GtkBuildable` interface
  * supports placing children into tabs by specifying “tab” as the
- * “type” attribute of a `<child>` element. Note that the content
+ * “type” attribute of a ``<child>`` element. Note that the content
  * of the tab must be created before the tab can be filled.
- * A tab child can be specified without specifying a `<child>`
+ * A tab child can be specified without specifying a ``<child>``
  * type attribute.
  *
  * To add a child widget in the notebooks action area, specify
  * "action-start" or “action-end” as the “type” attribute of the
- * `<child>` element.
+ * ``<child>`` element.
  *
  * An example of a UI definition fragment with `GtkNotebook`:
  *
  * ```xml
  * <object class="GtkNotebook">
- * <child>
+ * `<child>`
  * <object class="GtkLabel" id="notebook-content">
- * <property name="label">Content</property>
- * </object>
- * </child>
+ * <property name="label">Content`</property>`
+ * `</object>`
+ * `</child>`
  * <child type="tab">
  * <object class="GtkLabel" id="notebook-tab">
- * <property name="label">Tab</property>
- * </object>
- * </child>
- * </object>
+ * <property name="label">Tab`</property>`
+ * `</object>`
+ * `</child>`
+ * `</object>`
  * ```
  *
  * # Shortcuts and Gestures
@@ -3739,9 +3736,9 @@ export const MessageDialog = "MessageDialog";
  * │   ╰── [<action widget>]
  * │
  * ╰── stack
- * ├── <child>
+ * ├── `<child>`
  * ┊
- * ╰── <child>
+ * ╰── `<child>`
  * ```
  *
  * `GtkNotebook` has a main CSS node with name `notebook`, a subnode
@@ -3801,7 +3798,7 @@ export const Notebook = {
  *
  * The `GtkOverlay` implementation of the `GtkBuildable` interface
  * supports placing a child as an overlay by specifying “overlay” as
- * the “type” attribute of a `<child>` element.
+ * the “type” attribute of a ``<child>`` element.
  *
  * # CSS nodes
  *
@@ -3872,9 +3869,9 @@ export const PageSetupUnixDialog = "PageSetupUnixDialog";
  *
  * ```
  * paned
- * ├── <child>
+ * ├── `<child>`
  * ├── separator[.wide]
- * ╰── <child>
+ * ╰── `<child>`
  * ```
  *
  * `GtkPaned` has a main CSS node with name paned, and a subnode for
@@ -4064,7 +4061,7 @@ export const Picture = "Picture";
  * popover.background[.menu]
  * ├── arrow
  * ╰── contents
- * ╰── <child>
+ * ╰── `<child>`
  * ```
  *
  * `GtkPopover` has a main node with name `popover`, an arrow with name `arrow`,
@@ -4294,25 +4291,25 @@ export const PopoverMenuBar = "PopoverMenuBar";
  * <object class="GtkPrintUnixDialog" id="dialog1">
  * <child internal-child="notebook">
  * <object class="GtkNotebook" id="notebook">
- * <child>
+ * `<child>`
  * <object type="GtkNotebookPage">
- * <property name="tab_expand">False</property>
- * <property name="tab_fill">False</property>
+ * <property name="tab_expand">False`</property>`
+ * <property name="tab_fill">False`</property>`
  * <property name="tab">
  * <object class="GtkLabel" id="tablabel">
- * <property name="label">Tab label</property>
- * </object>
- * </property>
+ * <property name="label">Tab label`</property>`
+ * `</object>`
+ * `</property>`
  * <property name="child">
  * <object class="GtkLabel" id="tabcontent">
- * <property name="label">Content on notebook tab</property>
- * </object>
- * </property>
- * </object>
- * </child>
- * </object>
- * </child>
- * </object>
+ * <property name="label">Content on notebook tab`</property>`
+ * `</object>`
+ * `</property>`
+ * `</object>`
+ * `</child>`
+ * `</object>`
+ * `</child>`
+ * `</object>`
  * ```
  *
  * # CSS nodes
@@ -4802,7 +4799,7 @@ export const ShortcutLabel = "ShortcutLabel";
  * This widget is only meant to be used with [class@Gtk.ShortcutsWindow].
  *
  * The recommended way to construct a `GtkShortcutsGroup` is with
- * [class@Gtk.Builder], by using the `<child>` tag to populate a
+ * [class@Gtk.Builder], by using the ``<child>`` tag to populate a
  * `GtkShortcutsGroup` with one or more [class@Gtk.ShortcutsShortcut]
  * instances.
  *
@@ -4826,7 +4823,7 @@ export const ShortcutsGroup = "ShortcutsGroup";
  * This widget is only meant to be used with [class@Gtk.ShortcutsWindow].
  *
  * The recommended way to construct a `GtkShortcutsSection` is with
- * [class@Gtk.Builder], by using the `<child>` tag to populate a
+ * [class@Gtk.Builder], by using the ``<child>`` tag to populate a
  * `GtkShortcutsSection` with one or more [class@Gtk.ShortcutsGroup]
  * instances, which in turn contain one or more [class@Gtk.ShortcutsShortcut]
  * objects.
@@ -4861,7 +4858,7 @@ export const ShortcutsShortcut = "ShortcutsShortcut";
  * showing information that is not relevant in the current application context.
  *
  * The recommended way to construct a `GtkShortcutsWindow` is with
- * [class@Gtk.Builder], by using the `<child>` tag to populate a
+ * [class@Gtk.Builder], by using the ``<child>`` tag to populate a
  * `GtkShortcutsWindow` with one or more [class@Gtk.ShortcutsSection] objects,
  * which contain one or more [class@Gtk.ShortcutsGroup] instances, which, in turn,
  * contain [class@Gtk.ShortcutsShortcut] instances.
@@ -5090,17 +5087,17 @@ function StackVisibleChild(props) {
  *
  * ```xml
  * <object class="GtkStack" id="stack">
- * <child>
+ * `<child>`
  * <object class="GtkStackPage">
- * <property name="name">page1</property>
- * <property name="title">In the beginning…</property>
+ * <property name="name">page1`</property>`
+ * <property name="title">In the beginning…`</property>`
  * <property name="child">
  * <object class="GtkLabel">
- * <property name="label">It was dark</property>
- * </object>
- * </property>
- * </object>
- * </child>
+ * <property name="label">It was dark`</property>`
+ * `</object>`
+ * `</property>`
+ * `</object>`
+ * `</child>`
  * ```
  *
  * # CSS nodes
@@ -5586,7 +5583,7 @@ export const ToggleButton = {
  * treeexpander
  * ├── [indent]*
  * ├── [expander]
- * ╰── <child>
+ * ╰── `<child>`
  * ```
  *
  * `GtkTreeExpander` has zero or one CSS nodes with the name "expander" that
@@ -5639,31 +5636,31 @@ export const TreeExpander = "TreeExpander";
  * ## `GtkTreeView` as `GtkBuildable`
  *
  * The `GtkTreeView` implementation of the `GtkBuildable` interface accepts
- * [class@Gtk.TreeViewColumn] objects as `<child>` elements and exposes the
+ * [class@Gtk.TreeViewColumn] objects as ``<child>`` elements and exposes the
  * internal [class@Gtk.TreeSelection] in UI definitions.
  *
  * An example of a UI definition fragment with `GtkTreeView`:
  *
  * ```xml
  * <object class="GtkTreeView" id="treeview">
- * <property name="model">liststore1</property>
- * <child>
+ * <property name="model">liststore1`</property>`
+ * `<child>`
  * <object class="GtkTreeViewColumn" id="test-column">
- * <property name="title">Test</property>
- * <child>
+ * <property name="title">Test`</property>`
+ * `<child>`
  * <object class="GtkCellRendererText" id="test-renderer"/>
  * <attributes>
  * <attribute name="text">1</attribute>
  * </attributes>
- * </child>
- * </object>
- * </child>
+ * `</child>`
+ * `</object>`
+ * `</child>`
  * <child internal-child="selection">
  * <object class="GtkTreeSelection" id="selection">
  * <signal name="changed" handler="on_treeview_selection_changed"/>
- * </object>
- * </child>
- * </object>
+ * `</object>`
+ * `</child>`
+ * `</object>`
  * ```
  *
  * ## CSS nodes
@@ -5752,20 +5749,20 @@ export const VolumeButton = "VolumeButton";
  *
  * ```xml
  * <object class="GtkBox">
- * <child>
+ * `<child>`
  * <object class="GtkWindowControls">
- * <property name="side">start</property>
- * </object>
- * </child>
+ * <property name="side">start`</property>`
+ * `</object>`
+ * `</child>`
  *
  * ...
  *
- * <child>
+ * `<child>`
  * <object class="GtkWindowControls">
- * <property name="side">end</property>
- * </object>
- * </child>
- * </object>
+ * <property name="side">end`</property>`
+ * `</object>`
+ * `</child>`
+ * `</object>`
  * ```
  *
  * # CSS nodes
@@ -5810,6 +5807,3510 @@ export const WindowControls = "WindowControls";
  * role.
  */
 export const WindowHandle = "WindowHandle";
+/**
+ * A freeform window.
+ *
+ *
+ *
+ * The `AdwWindow` widget is a subclass of [class@Gtk.Window] which has no
+ * titlebar area. Instead, [class@ToolbarView] can be used together with
+ * [class@HeaderBar] or [class@Gtk.HeaderBar] as follows:
+ *
+ * ```xml
+ * <object class="AdwWindow">
+ * <property name="content">
+ * <object class="AdwToolbarView">
+ * <child type="top">
+ * <object class="AdwHeaderBar"/>
+ * `</child>`
+ * <property name="content">
+ * <!-- ... -->
+ * `</property>`
+ * `</object>`
+ * `</property>`
+ * `</object>`
+ * ```
+ *
+ * Using [property@Gtk.Window:titlebar] or [property@Gtk.Window:child]
+ * is not supported and will result in a crash. Use [property@Window:content]
+ * instead.
+ *
+ * ## Dialogs
+ *
+ * `AdwWindow` can contain [class@Dialog]. Use [method@Dialog.present] with the
+ * window or a widget within a window to show a dialog.
+ *
+ * ## Breakpoints
+ *
+ * `AdwWindow` can be used with [class@Breakpoint] the same way as
+ * [class@BreakpointBin]. Refer to that widget's documentation for details.
+ *
+ * Example:
+ *
+ * ```xml
+ * <object class="AdwWindow">
+ * <property name="content">
+ * <object class="AdwToolbarView">
+ * <child type="top">
+ * <object class="AdwHeaderBar"/>
+ * `</child>`
+ * <property name="content">
+ * <!-- ... -->
+ * `</property>`
+ * <child type="bottom">
+ * <object class="GtkActionBar" id="bottom_bar">
+ * <property name="revealed">True`</property>`
+ * <property name="visible">False`</property>`
+ * `</object>`
+ * `</child>`
+ * `</object>`
+ * `</property>`
+ * `<child>`
+ * <object class="AdwBreakpoint">
+ * <condition>max-width: 500px</condition>
+ * <setter object="bottom_bar" property="visible">True</setter>
+ * `</object>`
+ * `</child>`
+ * `</object>`
+ * ```
+ *
+ * When breakpoints are used, the minimum size must be larger than the smallest
+ * UI state. `AdwWindow` defaults to the minimum size of 360×200 px. If that's
+ * too small, set the [property@Gtk.Widget:width-request] and
+ * [property@Gtk.Widget:height-request] properties manually.
+ *
+ * ## Adaptive Preview
+ *
+ * `AdwWindow` has a debug tool called adaptive preview. It can be opened from
+ * GTK Inspector or by pressing `Ctrl`+`Shift`+`M`,
+ * and controlled via the [property@Window:adaptive-preview] property.
+ */
+export const AdwWindow = {
+    Root: "AdwWindow.Root",
+    Content: "AdwWindow.Content",
+};
+/**
+ * A dialog showing information about the application.
+ *
+ *
+ *
+ * an about dialog is typically opened when the user activates the `About …`
+ * item in the application's primary menu. All parts of the dialog are optional.
+ *
+ * ## Main page
+ *
+ * `AdwAboutDialog` prominently displays the application's icon, name, developer
+ * name and version. They can be set with the [property@AboutDialog:application-icon],
+ * [property@AboutDialog:application-name],
+ * [property@AboutDialog:developer-name] and [property@AboutDialog:version]
+ * respectively.
+ *
+ * ## What's New
+ *
+ * `AdwAboutDialog` provides a way for applications to display their release
+ * notes, set with the [property@AboutDialog:release-notes] property.
+ *
+ * Release notes are formatted the same way as
+ * AppStream descriptions.
+ *
+ * The supported formatting options are:
+ *
+ * * Paragraph (`<p>`)
+ * * Ordered list (`<ol>`), with list items (`<li>`)
+ * * Unordered list (`<ul>`), with list items (`<li>`)
+ *
+ * Within paragraphs and list items, emphasis (`<em>`) and inline code
+ * (`<code>`) text styles are supported. The emphasis is rendered in italic,
+ * while inline code is shown in a monospaced font.
+ *
+ * Any text outside paragraphs or list items is ignored.
+ *
+ * Nested lists are not supported.
+ *
+ * Only one version can be shown at a time. By default, the displayed version
+ * number matches [property@AboutDialog:version]. Use
+ * [property@AboutDialog:release-notes-version] to override it.
+ *
+ * ## Details
+ *
+ * The Details page displays the application comments and links.
+ *
+ * The comments can be set with the [property@AboutDialog:comments] property.
+ * Unlike [property@Gtk.AboutDialog:comments], this string can be long and
+ * detailed. It can also contain links and Pango markup.
+ *
+ * To set the application website, use [property@AboutDialog:website].
+ * To add extra links below the website, use [method@AboutDialog.add_link].
+ *
+ * If the Details page doesn't have any other content besides website, the
+ * website will be displayed on the main page instead.
+ *
+ * ## Troubleshooting
+ *
+ * `AdwAboutDialog` displays the following two links on the main page:
+ *
+ * * Support Questions, set with the [property@AboutDialog:support-url] property,
+ * * Report an Issue, set with the [property@AboutDialog:issue-url] property.
+ *
+ * Additionally, applications can provide debugging information. It will be
+ * shown separately on the Troubleshooting page. Use the
+ * [property@AboutDialog:debug-info] property to specify it.
+ *
+ * It's intended to be attached to issue reports when reporting issues against
+ * the application. As such, it cannot contain markup or links.
+ *
+ * `AdwAboutDialog` provides a quick way to save debug information to a file.
+ * When saving, [property@AboutDialog:debug-info-filename] would be used as
+ * the suggested filename.
+ *
+ * ## Credits and Acknowledgements
+ *
+ * The Credits page has the following default sections:
+ *
+ * * Developers, set with the [property@AboutDialog:developers] property,
+ * * Designers, set with the [property@AboutDialog:designers] property,
+ * * Artists, set with the [property@AboutDialog:artists] property,
+ * * Documenters, set with the [property@AboutDialog:documenters] property,
+ * * Translators, set with the [property@AboutDialog:translator-credits] property.
+ *
+ * When setting translator credits, use the strings `"translator-credits"` or
+ * `"translator_credits"` and mark them as translatable.
+ *
+ * The default sections that don't contain any names won't be displayed.
+ *
+ * The Credits page can also contain an arbitrary number of extra sections below
+ * the default ones. Use [method@AboutDialog.add_credit_section] to add them.
+ *
+ * The Acknowledgements page can be used to acknowledge additional people and
+ * organizations for their non-development contributions. Use
+ * [method@AboutDialog.add_acknowledgement_section] to add sections to it. For
+ * example, it can be used to list backers in a crowdfunded project or to give
+ * special thanks.
+ *
+ * Each of the people or organizations can have an email address or a website
+ * specified. To add a email address, use a string like
+ * `Edgar Allan Poe <edgar@poe.com>`. To specify a website with a title, use a
+ * string like `The GNOME Project https://www.gnome.org`:
+ *
+ *
+ *
+ * ## Legal
+ *
+ * The Legal page displays the copyright and licensing information for the
+ * application and other modules.
+ *
+ * The copyright string is set with the [property@AboutDialog:copyright]
+ * property and should be a short string of one or two lines, for example:
+ * `© 2022 Example`.
+ *
+ * Licensing information can be quickly set from a list of known licenses with
+ * the [property@AboutDialog:license-type] property. If the application's
+ * license is not in the list, [property@AboutDialog:license] can be used
+ * instead.
+ *
+ * To add information about other modules, such as application dependencies or
+ * data, use [method@AboutDialog.add_legal_section].
+ *
+ * ## Other applications
+ *
+ * `AdwAboutDialog` can show links to your other apps at the end of the main
+ * page. To add them, use [method@AboutDialog.add_other_app].
+ *
+ * ## Constructing
+ *
+ * To make constructing an `AdwAboutDialog` as convenient as possible, you can
+ * use the function [func@show_about_dialog] which constructs and shows a
+ * dialog.
+ *
+ * ```c
+ * static void
+ * show_about (GtkApplication *app)
+ * {
+ * const char *developers[] = {
+ * "Angela Avery",
+ * NULL
+ * };
+ *
+ * const char *designers[] = {
+ * "GNOME Design Team",
+ * NULL
+ * };
+ *
+ * adw_show_about_dialog (GTK_WIDGET (gtk_application_get_active_window (app)),
+ * "application-name", _("Example"),
+ * "application-icon", "org.example.App",
+ * "version", "1.2.3",
+ * "copyright", "© 2022 Angela Avery",
+ * "issue-url", "https://gitlab.gnome.org/example/example/-/issues/",
+ * "license-type", GTK_LICENSE_GPL_3_0,
+ * "developers", developers,
+ * "designers", designers,
+ * "translator-credits", _("translator-credits"),
+ * NULL);
+ * }
+ * ```
+ *
+ * ## CSS nodes
+ *
+ * `AdwAboutDialog` has a main CSS node with the name `dialog` and the
+ * style class `.about`.
+ */
+export const AdwAboutDialog = "AdwAboutDialog";
+/**
+ * A window showing information about the application.
+ *
+ *
+ *
+ * An about window is typically opened when the user activates the `About …`
+ * item in the application's primary menu. All parts of the window are optional.
+ *
+ * ## Main page
+ *
+ * `AdwAboutWindow` prominently displays the application's icon, name, developer
+ * name and version. They can be set with the [property@AboutWindow:application-icon],
+ * [property@AboutWindow:application-name],
+ * [property@AboutWindow:developer-name] and [property@AboutWindow:version]
+ * respectively.
+ *
+ * ## What's New
+ *
+ * `AdwAboutWindow` provides a way for applications to display their release
+ * notes, set with the [property@AboutWindow:release-notes] property.
+ *
+ * Release notes are formatted the same way as
+ * AppStream descriptions.
+ *
+ * The supported formatting options are:
+ *
+ * * Paragraph (`<p>`)
+ * * Ordered list (`<ol>`), with list items (`<li>`)
+ * * Unordered list (`<ul>`), with list items (`<li>`)
+ *
+ * Within paragraphs and list items, emphasis (`<em>`) and inline code
+ * (`<code>`) text styles are supported. The emphasis is rendered in italic,
+ * while inline code is shown in a monospaced font.
+ *
+ * Any text outside paragraphs or list items is ignored.
+ *
+ * Nested lists are not supported.
+ *
+ * Only one version can be shown at a time. By default, the displayed version
+ * number matches [property@AboutWindow:version]. Use
+ * [property@AboutWindow:release-notes-version] to override it.
+ *
+ * ## Details
+ *
+ * The Details page displays the application comments and links.
+ *
+ * The comments can be set with the [property@AboutWindow:comments] property.
+ * Unlike [property@Gtk.AboutDialog:comments], this string can be long and
+ * detailed. It can also contain links and Pango markup.
+ *
+ * To set the application website, use [property@AboutWindow:website].
+ * To add extra links below the website, use [method@AboutWindow.add_link].
+ *
+ * If the Details page doesn't have any other content besides website, the
+ * website will be displayed on the main page instead.
+ *
+ * ## Troubleshooting
+ *
+ * `AdwAboutWindow` displays the following two links on the main page:
+ *
+ * * Support Questions, set with the [property@AboutWindow:support-url] property,
+ * * Report an Issue, set with the [property@AboutWindow:issue-url] property.
+ *
+ * Additionally, applications can provide debugging information. It will be
+ * shown separately on the Troubleshooting page. Use the
+ * [property@AboutWindow:debug-info] property to specify it.
+ *
+ * It's intended to be attached to issue reports when reporting issues against
+ * the application. As such, it cannot contain markup or links.
+ *
+ * `AdwAboutWindow` provides a quick way to save debug information to a file.
+ * When saving, [property@AboutWindow:debug-info-filename] would be used as
+ * the suggested filename.
+ *
+ * ## Credits and Acknowledgements
+ *
+ * The Credits page has the following default sections:
+ *
+ * * Developers, set with the [property@AboutWindow:developers] property,
+ * * Designers, set with the [property@AboutWindow:designers] property,
+ * * Artists, set with the [property@AboutWindow:artists] property,
+ * * Documenters, set with the [property@AboutWindow:documenters] property,
+ * * Translators, set with the [property@AboutWindow:translator-credits] property.
+ *
+ * When setting translator credits, use the strings `"translator-credits"` or
+ * `"translator_credits"` and mark them as translatable.
+ *
+ * The default sections that don't contain any names won't be displayed.
+ *
+ * The Credits page can also contain an arbitrary number of extra sections below
+ * the default ones. Use [method@AboutWindow.add_credit_section] to add them.
+ *
+ * The Acknowledgements page can be used to acknowledge additional people and
+ * organizations for their non-development contributions. Use
+ * [method@AboutWindow.add_acknowledgement_section] to add sections to it. For
+ * example, it can be used to list backers in a crowdfunded project or to give
+ * special thanks.
+ *
+ * Each of the people or organizations can have an email address or a website
+ * specified. To add a email address, use a string like
+ * `Edgar Allan Poe <edgar@poe.com>`. To specify a website with a title, use a
+ * string like `The GNOME Project https://www.gnome.org`:
+ *
+ *
+ *
+ * ## Legal
+ *
+ * The Legal page displays the copyright and licensing information for the
+ * application and other modules.
+ *
+ * The copyright string is set with the [property@AboutWindow:copyright]
+ * property and should be a short string of one or two lines, for example:
+ * `© 2022 Example`.
+ *
+ * Licensing information can be quickly set from a list of known licenses with
+ * the [property@AboutWindow:license-type] property. If the application's
+ * license is not in the list, [property@AboutWindow:license] can be used
+ * instead.
+ *
+ * To add information about other modules, such as application dependencies or
+ * data, use [method@AboutWindow.add_legal_section].
+ *
+ * ## Constructing
+ *
+ * To make constructing an `AdwAboutWindow` as convenient as possible, you can
+ * use the function [func@show_about_window] which constructs and shows a
+ * window.
+ *
+ * ```c
+ * static void
+ * show_about (GtkApplication *app)
+ * {
+ * const char *developers[] = {
+ * "Angela Avery",
+ * NULL
+ * };
+ *
+ * const char *designers[] = {
+ * "GNOME Design Team",
+ * NULL
+ * };
+ *
+ * adw_show_about_window (gtk_application_get_active_window (app),
+ * "application-name", _("Example"),
+ * "application-icon", "org.example.App",
+ * "version", "1.2.3",
+ * "copyright", "© 2022 Angela Avery",
+ * "issue-url", "https://gitlab.gnome.org/example/example/-/issues/",
+ * "license-type", GTK_LICENSE_GPL_3_0,
+ * "developers", developers,
+ * "designers", designers,
+ * "translator-credits", _("translator-credits"),
+ * NULL);
+ * }
+ * ```
+ *
+ * ## CSS nodes
+ *
+ * `AdwAboutWindow` has a main CSS node with the name `window` and the
+ * style class `.about`.
+ */
+export const AdwAboutWindow = "AdwAboutWindow";
+/**
+ * A [class@Gtk.ListBoxRow] used to present actions.
+ *
+ *
+ *
+ * The `AdwActionRow` widget can have a title, a subtitle and an icon. The row
+ * can receive additional widgets at its end, or prefix widgets at its start.
+ *
+ * It is convenient to present a preference and its related actions.
+ *
+ * `AdwActionRow` is unactivatable by default, giving it an activatable widget
+ * will automatically make it activatable, but unsetting it won't change the
+ * row's activatability.
+ *
+ * ## AdwActionRow as GtkBuildable
+ *
+ * The `AdwActionRow` implementation of the [iface@Gtk.Buildable] interface
+ * supports adding a child at its end by specifying “suffix” or omitting the
+ * “type” attribute of a `<child>` element.
+ *
+ * It also supports adding a child as a prefix widget by specifying “prefix” as
+ * the “type” attribute of a `<child>` element.
+ *
+ * ## CSS nodes
+ *
+ * `AdwActionRow` has a main CSS node with name `row`.
+ *
+ * It contains the subnode `box.header` for its main horizontal box, and
+ * `box.title` for the vertical box containing the title and subtitle labels.
+ *
+ * It contains subnodes `label.title` and `label.subtitle` representing
+ * respectively the title label and subtitle label.
+ *
+ * ## Style classes
+ *
+ * `AdwActionRow` can use the `.property`
+ * style class to emphasize the row subtitle instead of the row title, which is
+ * useful for displaying read-only properties.
+ *
+ *
+ *
+ * When used together with the `.monospace` style class, only the subtitle
+ * becomes monospace, not the title or any extra widgets.
+ */
+export const AdwActionRow = {
+    Root: "AdwActionRow.Root",
+    ActivatableWidget: "AdwActionRow.ActivatableWidget",
+};
+/**
+ * A dialog presenting a message or a question.
+ *
+ *
+ *
+ * Alert dialogs have a heading, a body, an optional child widget, and one or
+ * multiple responses, each presented as a button.
+ *
+ * Each response has a unique string ID, and a button label. Additionally, each
+ * response can be enabled or disabled, and can have a suggested or destructive
+ * appearance.
+ *
+ * When one of the responses is activated, or the dialog is closed, the
+ * [signal@AlertDialog::response] signal will be emitted. This signal is
+ * detailed, and the detail, as well as the `response` parameter will be set to
+ * the ID of the activated response, or to the value of the
+ * [property@AlertDialog:close-response] property if the dialog had been closed
+ * without activating any of the responses.
+ *
+ * Response buttons can be presented horizontally or vertically depending on
+ * available space.
+ *
+ * When a response is activated, `AdwAlertDialog` is closed automatically.
+ *
+ * An example of using an alert dialog:
+ *
+ * ```c
+ * AdwDialog *dialog;
+ *
+ * dialog = adw_alert_dialog_new (_("Replace File?"), NULL);
+ *
+ * adw_alert_dialog_format_body (ADW_ALERT_DIALOG (dialog),
+ * _("A file named “%s” already exists. Do you want to replace it?"),
+ * filename);
+ *
+ * adw_alert_dialog_add_responses (ADW_ALERT_DIALOG (dialog),
+ * "cancel",  _("_Cancel"),
+ * "replace", _("_Replace"),
+ * NULL);
+ *
+ * adw_alert_dialog_set_response_appearance (ADW_ALERT_DIALOG (dialog),
+ * "replace",
+ * ADW_RESPONSE_DESTRUCTIVE);
+ *
+ * adw_alert_dialog_set_default_response (ADW_ALERT_DIALOG (dialog), "cancel");
+ * adw_alert_dialog_set_close_response (ADW_ALERT_DIALOG (dialog), "cancel");
+ *
+ * g_signal_connect (dialog, "response", G_CALLBACK (response_cb), self);
+ *
+ * adw_dialog_present (dialog, parent);
+ * ```
+ *
+ * ## Async API
+ *
+ * `AdwAlertDialog` can also be used via the [method@AlertDialog.choose] method.
+ * This API follows the GIO async pattern, for example:
+ *
+ * ```c
+ * static void
+ * dialog_cb (AdwAlertDialog *dialog,
+ * GAsyncResult   *result,
+ * MyWindow       *self)
+ * {
+ * const char *response = adw_alert_dialog_choose_finish (dialog, result);
+ *
+ * // ...
+ * }
+ *
+ * static void
+ * show_dialog (MyWindow *self)
+ * {
+ * AdwDialog *dialog;
+ *
+ * dialog = adw_alert_dialog_new (_("Replace File?"), NULL);
+ *
+ * adw_alert_dialog_format_body (ADW_ALERT_DIALOG (dialog),
+ * _("A file named “%s” already exists. Do you want to replace it?"),
+ * filename);
+ *
+ * adw_alert_dialog_add_responses (ADW_ALERT_DIALOG (dialog),
+ * "cancel",  _("_Cancel"),
+ * "replace", _("_Replace"),
+ * NULL);
+ *
+ * adw_alert_dialog_set_response_appearance (ADW_ALERT_DIALOG (dialog),
+ * "replace",
+ * ADW_RESPONSE_DESTRUCTIVE);
+ *
+ * adw_alert_dialog_set_default_response (ADW_ALERT_DIALOG (dialog), "cancel");
+ * adw_alert_dialog_set_close_response (ADW_ALERT_DIALOG (dialog), "cancel");
+ *
+ * adw_alert_dialog_choose (ADW_ALERT_DIALOG (dialog), GTK_WIDGET (self),
+ * NULL, (GAsyncReadyCallback) dialog_cb, self);
+ * }
+ * ```
+ *
+ * ## AdwAlertDialog as GtkBuildable
+ *
+ * `AdwAlertDialog` supports adding responses in UI definitions by via the
+ * `<responses>` element that may contain multiple `<response>` elements, each
+ * representing a response.
+ *
+ * Each of the `<response>` elements must have the `id` attribute specifying the
+ * response ID. The contents of the element are used as the response label.
+ *
+ * Response labels can be translated with the usual `translatable`, `context`
+ * and `comments` attributes.
+ *
+ * The `<response>` elements can also have `enabled` and/or `appearance`
+ * attributes. See [method@AlertDialog.set_response_enabled] and
+ * [method@AlertDialog.set_response_appearance] for details.
+ *
+ * Example of an `AdwAlertDialog` UI definition:
+ *
+ * ```xml
+ * <object class="AdwAlertDialog" id="dialog">
+ * <property name="heading" translatable="yes">Save Changes?`</property>`
+ * <property name="body" translatable="yes">Open documents contain unsaved changes. Changes which are not saved will be permanently lost.`</property>`
+ * <property name="default-response">save`</property>`
+ * <property name="close-response">cancel`</property>`
+ * <signal name="response" handler="response_cb"/>
+ * <responses>
+ * <response id="cancel" translatable="yes">_Cancel</response>
+ * <response id="discard" translatable="yes" appearance="destructive">_Discard</response>
+ * <response id="save" translatable="yes" appearance="suggested" enabled="false">_Save</response>
+ * </responses>
+ * `</object>`
+ * ```
+ */
+export const AdwAlertDialog = {
+    Root: "AdwAlertDialog.Root",
+    ExtraChild: "AdwAlertDialog.ExtraChild",
+};
+/**
+ * A freeform application window.
+ *
+ *
+ *
+ * `AdwApplicationWindow` is a [class@Gtk.ApplicationWindow] subclass providing
+ * the same features as [class@Window].
+ *
+ * See [class@Window] for details.
+ *
+ * Example of an `AdwApplicationWindow` UI definition:
+ *
+ * ```xml
+ * <object class="AdwApplicationWindow">
+ * <property name="content">
+ * <object class="AdwToolbarView">
+ * <child type="top">
+ * <object class="AdwHeaderBar"/>
+ * `</child>`
+ * <property name="content">
+ * <!-- ... -->
+ * `</property>`
+ * `</object>`
+ * `</property>`
+ * `</object>`
+ * ```
+ *
+ * Using [property@Gtk.Application:menubar] is not supported and may result in
+ * visual glitches.
+ */
+export const AdwApplicationWindow = {
+    Root: "AdwApplicationWindow.Root",
+    Content: "AdwApplicationWindow.Content",
+};
+/**
+ * A widget displaying an image, with a generated fallback.
+ *
+ *
+ *
+ * `AdwAvatar` is a widget that shows a round avatar.
+ *
+ * `AdwAvatar` generates an avatar with the initials of  the
+ * [property@Avatar:text] on top of a colored background.
+ *
+ * The color is picked based on the hash of the [property@Avatar:text].
+ *
+ * If [property@Avatar:show-initials] is set to `FALSE`,
+ * [property@Avatar:icon-name] or `avatar-default-symbolic` is shown instead of
+ * the initials.
+ *
+ * Use [property@Avatar:custom-image] to set a custom image.
+ *
+ * ## CSS nodes
+ *
+ * `AdwAvatar` has a single CSS node with name `avatar`.
+ *
+ * ## Accessibility
+ *
+ * `AdwAvatar` uses the `GTK_ACCESSIBLE_ROLE_IMG` role.
+ */
+export const AdwAvatar = "AdwAvatar";
+/**
+ * A bar with contextual information.
+ *
+ *
+ *
+ * Banners are hidden by default, use [property@Banner:revealed] to show them.
+ *
+ * Banners have a title, set with [property@Banner:title]. Titles can be marked
+ * up with Pango markup, use [property@Banner:use-markup] to enable it.
+ *
+ * The title will be shown centered or left-aligned depending on available
+ * space.
+ *
+ * Banners can optionally have a button with text on it, set through
+ * [property@Banner:button-label]. The button can be used with a `GAction`,
+ * or with the [signal@Banner::button-clicked] signal. The button can have
+ * different styles, a gray style and a suggested style.
+ *
+ *
+ *
+ * ## CSS nodes
+ *
+ * `AdwBanner` has a main CSS node with the name `banner`.
+ */
+export const AdwBanner = "AdwBanner";
+/**
+ * A widget with one child.
+ *
+ *
+ *
+ * The `AdwBin` widget has only one child, set with the [property@Bin:child]
+ * property.
+ *
+ * It is useful for deriving subclasses, since it provides common code needed
+ * for handling a single child widget.
+ */
+export const AdwBin = "AdwBin";
+/**
+ * A bottom sheet with an optional bottom bar.
+ *
+ *
+ *
+ * `AdwBottomSheet` has three child widgets. [property@BottomSheet:content] is
+ * shown persistently. [property@BottomSheet:sheet] is displayed above it when
+ * it's open, and [property@BottomSheet:bottom-bar] is displayed when it's not.
+ *
+ * Bottom sheet and bottom bar are attached to the bottom edge of the widget.
+ * They take the full width by default, but can only take a portion of it if
+ * [property@BottomSheet:full-width] is set to `FALSE`. In this case,
+ * [property@BottomSheet:align] determines where along the bottom edge they are
+ * placed.
+ *
+ * Bottom bar can be hidden using the [property@BottomSheet:reveal-bottom-bar]
+ * property.
+ *
+ * `AdwBottomSheet` can be useful for applications such as music players, that
+ * want to have a persistent bottom bar that expands into a bottom sheet when
+ * clicked. It's meant for cases where a bottom sheet is tightly integrated into
+ * the UI. For more transient bottom sheets, see [class@Dialog].
+ *
+ * To open or close the bottom sheet, use the [property@BottomSheet:open]
+ * property.
+ *
+ * By default, the bottom sheet has an overlaid drag handle. It can be disabled
+ * by setting [property@BottomSheet:show-drag-handle] to `FALSE`. Note that the
+ * handle also controls whether the sheet can be dragged using a pointer.
+ *
+ * Bottom sheets are modal by default, meaning that the content is dimmed and
+ * cannot be accessed while the sheet is open. Set [property@BottomSheet:modal]
+ * to `FALSE` if this behavior is unwanted.
+ *
+ * To disable user interactions for opening or closing the bottom sheet (such as
+ * swipes or clicking the bottom bar or close button), set
+ * [property@BottomSheet:can-open] or [property@BottomSheet:can-close] to
+ * `FALSE`.
+ *
+ * In some cases, particularly when using a full-width bottom bar, it may be
+ * necessary to shift [property@BottomSheet:content] upwards. Use the
+ * [property@BottomSheet:bottom-bar-height] and
+ * [property@BottomSheet:sheet-height] for that.
+ *
+ * `AdwBottomSheet` is not adaptive, and for larger window sizes applications
+ * may want to replace it with another UI, such as a sidebar. This can be done
+ * using [class@MultiLayoutView].
+ *
+ * ## Sizing
+ *
+ * Unlike [class@Dialog] presented as a bottom sheet, `AdwBottomSheet` just
+ * follows the content's natural size, and it's up to the applications to make
+ * sure their content provides one. For example, when using
+ * [class@Gtk.ScrolledWindow], make sure to set
+ * [property@Gtk.ScrolledWindow:propagate-natural-height] to `TRUE`.
+ *
+ * ## Header Bar Integration
+ *
+ * When placed inside an `AdwBottomSheet`, [class@HeaderBar] will not show the
+ * title when [property@BottomSheet:show-drag-handle] is `TRUE`, regardless of
+ * [property@HeaderBar:show-title]. This only applies to the default title,
+ * titles set with [property@HeaderBar:title-widget] will still be shown.
+ *
+ * ## `AdwBottomSheet` as `GtkBuildable`:
+ *
+ * The `AdwBottomSheet` implementation of the [iface@Gtk.Buildable] interface
+ * supports setting the sheet widget by specifying “sheet” as the “type”
+ * attribute of a ``<child>`` element, and the bottom bar by specifying
+ * “bottom-bar”. Specifying “content” or omitting the child type results in
+ * setting the content child.
+ */
+export const AdwBottomSheet = {
+    Root: "AdwBottomSheet.Root",
+    BottomBar: "AdwBottomSheet.BottomBar",
+    Content: "AdwBottomSheet.Content",
+    Sheet: "AdwBottomSheet.Sheet",
+};
+/**
+ * A widget that changes layout based on available size.
+ *
+ *
+ *
+ * `AdwBreakpointBin` provides a way to use breakpoints without [class@Window],
+ * [class@ApplicationWindow] or [class@Dialog]. It can be useful for limiting
+ * breakpoints to a single page and similar purposes. Most applications
+ * shouldn't need it.
+ *
+ * `AdwBreakpointBin` is similar to [class@Bin]. It has one child, set via the
+ * [property@BreakpointBin:child] property.
+ *
+ * When `AdwBreakpointBin` is resized, its child widget can rearrange its layout
+ * at specific thresholds.
+ *
+ * The thresholds and layout changes are defined via [class@Breakpoint] objects.
+ * They can be added using [method@BreakpointBin.add_breakpoint].
+ *
+ * Each breakpoint has a condition, specifying the bin's size and/or aspect
+ * ratio, and setters that automatically set object properties when that
+ * happens. The [signal@Breakpoint::apply] and [signal@Breakpoint::unapply] can
+ * be used instead for more complex scenarios.
+ *
+ * Breakpoints are only allowed to modify widgets inside the `AdwBreakpointBin`,
+ * but not on the `AdwBreakpointBin` itself or any other widgets.
+ *
+ * If multiple breakpoints can be used for the current size, the last one is
+ * always picked. The current breakpoint can be tracked using the
+ * [property@BreakpointBin:current-breakpoint] property.
+ *
+ * If none of the breakpoints can be used, that property will be set to `NULL`,
+ * and the original property values will be used instead.
+ *
+ * ## Minimum Size
+ *
+ * Adding a breakpoint to `AdwBreakpointBin` will result in it having no minimum
+ * size. The [property@Gtk.Widget:width-request] and
+ * [property@Gtk.Widget:height-request] properties must always be set when using
+ * breakpoints, indicating the smallest size you want to support.
+ *
+ * The minimum size and breakpoint conditions must be carefully selected so that
+ * the child widget completely fits. If it doesn't, it will overflow and a
+ * warning message will be printed.
+ *
+ * When choosing minimum size, consider translations and text scale factor
+ * changes. Make sure to leave enough space for text labels, and enable
+ * ellipsizing or wrapping if they might not fit.
+ *
+ * For [class@Gtk.Label] this can be done via [property@Gtk.Label:ellipsize], or
+ * via [property@Gtk.Label:wrap] together with [property@Gtk.Label:wrap-mode].
+ *
+ * For buttons, use [property@Gtk.Button:can-shrink],
+ * [property@Gtk.MenuButton:can-shrink], [property@Adw.SplitButton:can-shrink],
+ * or [property@Adw.ButtonContent:can-shrink].
+ *
+ * ## Example
+ *
+ * ```c
+ * GtkWidget *bin, *child;
+ * AdwBreakpoint *breakpoint;
+ *
+ * bin = adw_breakpoint_bin_new ();
+ * gtk_widget_set_size_request (bin, 150, 150);
+ *
+ * child = gtk_label_new ("Wide");
+ * gtk_label_set_ellipsize (GTK_LABEL (label), PANGO_ELLIPSIZE_END);
+ * gtk_widget_add_css_class (child, "title-1");
+ * adw_breakpoint_bin_set_child (ADW_BREAKPOINT_BIN (bin), child);
+ *
+ * breakpoint = adw_breakpoint_new (adw_breakpoint_condition_parse ("max-width: 200px"));
+ * adw_breakpoint_add_setters (breakpoint,
+ * G_OBJECT (child), "label", "Narrow",
+ * NULL);
+ * adw_breakpoint_bin_add_breakpoint (ADW_BREAKPOINT_BIN (bin), breakpoint);
+ * ```
+ *
+ * The bin has a single label inside it, displaying "Wide". When the bin's width
+ * is smaller than or equal to 200px, it changes to "Narrow".
+ *
+ * ## `AdwBreakpointBin` as `GtkBuildable`
+ *
+ * `AdwBreakpointBin` allows adding `AdwBreakpoint` objects as children.
+ *
+ * Example of an `AdwBreakpointBin` UI definition:
+ *
+ * ```xml
+ * <object class="AdwBreakpointBin">
+ * <property name="width-request">150`</property>`
+ * <property name="height-request">150`</property>`
+ * <property name="child">
+ * <object class="GtkLabel" id="child">
+ * <property name="label">Wide`</property>`
+ * <property name="ellipsize">end`</property>`
+ * <style>
+ * <class name="title-1"/>
+ * </style>
+ * `</object>`
+ * `</property>`
+ * `<child>`
+ * <object class="AdwBreakpoint">
+ * <condition>max-width: 200px</condition>
+ * <setter object="child" property="label">Narrow</setter>
+ * `</object>`
+ * `</child>`
+ * `</object>`
+ * ```
+ *
+ * See [class@Breakpoint] documentation for details.
+ */
+export const AdwBreakpointBin = "AdwBreakpointBin";
+/**
+ * A helper widget for creating buttons.
+ *
+ *
+ *
+ * `AdwButtonContent` is a box-like widget with an icon and a label.
+ *
+ * It's intended to be used as a direct child of [class@Gtk.Button],
+ * [class@Gtk.MenuButton] or [class@SplitButton], when they need to have both an
+ * icon and a label, as follows:
+ *
+ * ```xml
+ * <object class="GtkButton">
+ * <property name="child">
+ * <object class="AdwButtonContent">
+ * <property name="icon-name">document-open-symbolic`</property>`
+ * <property name="label" translatable="yes">_Open`</property>`
+ * <property name="use-underline">True`</property>`
+ * `</object>`
+ * `</property>`
+ * `</object>`
+ * ```
+ *
+ * `AdwButtonContent` handles style classes and connecting the mnemonic to the
+ * button automatically.
+ *
+ * ## CSS nodes
+ *
+ * ```
+ * buttoncontent
+ * ╰── box
+ * ├── image
+ * ╰── label
+ * ```
+ *
+ * `AdwButtonContent`'s CSS node is called `buttoncontent`. It contains a `box`
+ * subnode that serves as a container for the  `image` and `label` nodes.
+ *
+ * When inside a `GtkButton` or `AdwSplitButton`, the button will receive the
+ * `.image-text-button` style class. When inside a `GtkMenuButton`, the
+ * internal `GtkButton` will receive it instead.
+ *
+ * ## Accessibility
+ *
+ * `AdwButtonContent` uses the `GTK_ACCESSIBLE_ROLE_GROUP` role.
+ */
+export const AdwButtonContent = "AdwButtonContent";
+/**
+ * A [class@Gtk.ListBoxRow] that looks like a button.
+ *
+ *
+ *
+ * The `AdwButtonRow` widget has a title and two icons: before and after the
+ * title.
+ *
+ * It is convenient for presenting actions like "Delete" at the end of a boxed
+ * list.
+ *
+ * `AdwButtonRow` is always activatable.
+ *
+ * ## CSS nodes
+ *
+ * `AdwButtonRow` has a main CSS node with name `row` and the style class
+ * `.button`.
+ *
+ * It contains the subnode `box` for its main horizontal box, which contains the
+ * nodes: `image.icon.start` for the start icon, `label.title` for the title,
+ * and `image.icon.end` for the end icon.
+ *
+ * ## Style classes
+ *
+ * The `.suggested-action` style class
+ * makes `AdwButtonRow` use accent color for its background. It should be used
+ * very sparingly to denote important buttons.
+ *
+ *
+ *
+ * The `.destructive-action` style
+ * makes the row use destructive colors. It can be used to draw attention to the
+ * potentially damaging consequences of using it. This style acts as a warning
+ * to the user.
+ */
+export const AdwButtonRow = "AdwButtonRow";
+/**
+ * A paginated scrolling widget.
+ *
+ *
+ *
+ * The `AdwCarousel` widget can be used to display a set of pages with
+ * swipe-based navigation between them.
+ *
+ * [class@CarouselIndicatorDots] and [class@CarouselIndicatorLines] can be used
+ * to provide page indicators for `AdwCarousel`.
+ *
+ * ## CSS nodes
+ *
+ * `AdwCarousel` has a single CSS node with name `carousel`.
+ */
+export const AdwCarousel = "AdwCarousel";
+/**
+ * A dots indicator for [class@Carousel].
+ *
+ *
+ *
+ * The `AdwCarouselIndicatorDots` widget shows a set of dots for each page of a
+ * given [class@Carousel]. The dot representing the carousel's active page is
+ * larger and more opaque than the others, the transition to the active and
+ * inactive state is gradual to match the carousel's position.
+ *
+ * See also [class@CarouselIndicatorLines].
+ *
+ * ## CSS nodes
+ *
+ * `AdwCarouselIndicatorDots` has a single CSS node with name
+ * `carouselindicatordots`.
+ */
+export const AdwCarouselIndicatorDots = "AdwCarouselIndicatorDots";
+/**
+ * A lines indicator for [class@Carousel].
+ *
+ *
+ *
+ * The `AdwCarouselIndicatorLines` widget shows a set of lines for each page of
+ * a given [class@Carousel]. The carousel's active page is shown as another line
+ * that moves between them to match the carousel's position.
+ *
+ * See also [class@CarouselIndicatorDots].
+ *
+ * ## CSS nodes
+ *
+ * `AdwCarouselIndicatorLines` has a single CSS node with name
+ * `carouselindicatorlines`.
+ */
+export const AdwCarouselIndicatorLines = "AdwCarouselIndicatorLines";
+/**
+ * A widget constraining its child to a given size.
+ *
+ *
+ *
+ *
+ * The `AdwClamp` widget constrains the size of the widget it contains to a
+ * given maximum size. It will constrain the width if it is horizontal, or the
+ * height if it is vertical. The expansion of the child from its minimum to its
+ * maximum size is eased out for a smooth transition.
+ *
+ * If the child requires more than the requested maximum size, it will be
+ * allocated the minimum size it can fit in instead.
+ *
+ * `AdwClamp` can scale with the text scale factor, use the
+ * [property@Clamp:unit] property to enable that behavior.
+ *
+ * See also: [class@ClampLayout], [class@ClampScrollable].
+ *
+ * ## CSS nodes
+ *
+ * `AdwClamp` has a single CSS node with name `clamp`.
+ */
+export const AdwClamp = "AdwClamp";
+/**
+ * A scrollable [class@Clamp].
+ *
+ * `AdwClampScrollable` is a variant of [class@Clamp] that implements the
+ * [iface@Gtk.Scrollable] interface.
+ *
+ * The primary use case for `AdwClampScrollable` is clamping
+ * [class@Gtk.ListView].
+ *
+ * See also: [class@ClampLayout].
+ */
+export const AdwClampScrollable = "AdwClampScrollable";
+/**
+ * A [class@Gtk.ListBoxRow] used to choose from a list of items.
+ *
+ *
+ *
+ * The `AdwComboRow` widget allows the user to choose from a list of valid
+ * choices. The row displays the selected choice. When activated, the row
+ * displays a popover which allows the user to make a new choice.
+ *
+ * Example of an `AdwComboRow` UI definition:
+ * ```xml
+ * <object class="AdwComboRow">
+ * <property name="title" translatable="yes">Combo Row`</property>`
+ * <property name="model">
+ * <object class="GtkStringList">
+ * <items>
+ * <item translatable="yes">Foo</item>
+ * <item translatable="yes">Bar</item>
+ * <item translatable="yes">Baz</item>
+ * </items>
+ * `</object>`
+ * `</property>`
+ * `</object>`
+ * ```
+ *
+ * The [property@ComboRow:selected] and [property@ComboRow:selected-item]
+ * properties can be used to keep track of the selected item and react to their
+ * changes.
+ *
+ * `AdwComboRow` mirrors [class@Gtk.DropDown], see that widget for details.
+ *
+ * `AdwComboRow` is [property@Gtk.ListBoxRow:activatable] if a model is set.
+ *
+ * ## CSS nodes
+ *
+ * `AdwComboRow` has a main CSS node with name `row` and the `.combo` style
+ * class.
+ *
+ * Its popover has the node named `popover` with the `.menu` style class, it
+ * contains a [class@Gtk.ScrolledWindow], which in turn contains a
+ * [class@Gtk.ListView], both are accessible via their regular nodes.
+ *
+ * ## Accessibility
+ *
+ * `AdwComboRow` uses the `GTK_ACCESSIBLE_ROLE_COMBO_BOX` role.
+ */
+export const AdwComboRow = "AdwComboRow";
+/**
+ * An adaptive dialog container.
+ *
+ *
+ *
+ *
+ * `AdwDialog` is similar to a window, but is shown within another window. It
+ * can be used with [class@Window] and [class@ApplicationWindow], use
+ * [method@Dialog.present] to show it.
+ *
+ * `AdwDialog` is not resizable. Use the [property@Dialog:content-width] and
+ * [property@Dialog:content-height] properties to set its size, or set
+ * [property@Dialog:follows-content-size] to `TRUE` to make the dialog track the
+ * content's size as it changes. `AdwDialog` can never be larger than its parent
+ * window.
+ *
+ * `AdwDialog` can be presented as a centered floating window or a bottom sheet.
+ * By default it's automatic depending on the available size.
+ * [property@Dialog:presentation-mode] can be used to change that.
+ *
+ * `AdwDialog` can be closed via [method@Dialog.close].
+ *
+ * When presented as a bottom sheet, `AdwDialog` can also be closed via swiping
+ * it down.
+ *
+ * The [property@Dialog:can-close] can be used to prevent closing. In that case,
+ * [signal@Dialog::close-attempt] gets emitted instead.
+ *
+ * Use [method@Dialog.force_close] to close the dialog even when `can-close` is set to
+ * `FALSE`.
+ *
+ * `AdwDialog` is transient and doesn't integrate with the window below it, for
+ * example it's not possible to collapse it into a bottom bar. See
+ * [class@BottomSheet] for persistent and more tightly integrated bottom sheets.
+ *
+ * ## Header Bar Integration
+ *
+ * When placed inside an `AdwDialog`, [class@HeaderBar] will display the dialog
+ * title instead of window title. It will also adjust the decoration layout to
+ * ensure it always has a close button and nothing else. Set
+ * [property@HeaderBar:show-start-title-buttons] and
+ * [property@HeaderBar:show-end-title-buttons] to `FALSE` to remove it if it's
+ * unwanted.
+ *
+ * ## Breakpoints
+ *
+ * `AdwDialog` can be used with [class@Breakpoint] the same way as
+ * [class@BreakpointBin]. Refer to that widget's documentation for details.
+ *
+ * Like `AdwBreakpointBin`, if breakpoints are used, `AdwDialog` doesn't have a
+ * minimum size, and [property@Gtk.Widget:width-request] and
+ * [property@Gtk.Widget:height-request] properties must be set manually.
+ */
+export const AdwDialog = {
+    Root: "AdwDialog.Root",
+    Child: "AdwDialog.Child",
+    DefaultWidget: "AdwDialog.DefaultWidget",
+    FocusWidget: "AdwDialog.FocusWidget",
+};
+/**
+ * A [class@Gtk.ListBoxRow] with an embedded text entry.
+ *
+ *
+ *
+ * `AdwEntryRow` has a title that doubles as placeholder text. It shows an icon
+ * indicating that it's editable and can receive additional widgets before or
+ * after the editable part.
+ *
+ * If [property@EntryRow:show-apply-button] is set to `TRUE`, `AdwEntryRow` can
+ * show an apply button when editing its contents. This can be useful if
+ * changing its contents can result in an expensive operation, such as network
+ * activity.
+ *
+ * `AdwEntryRow` provides only minimal API and should be used with the
+ * [iface@Gtk.Editable] API.
+ *
+ * See also [class@PasswordEntryRow].
+ *
+ * ## AdwEntryRow as GtkBuildable
+ *
+ * The `AdwEntryRow` implementation of the [iface@Gtk.Buildable] interface
+ * supports adding a child at its end by specifying “suffix” or omitting the
+ * “type” attribute of a `<child>` element.
+ *
+ * It also supports adding a child as a prefix widget by specifying “prefix” as
+ * the “type” attribute of a `<child>` element.
+ *
+ * ## CSS nodes
+ *
+ * `AdwEntryRow` has a single CSS node with name `row` and the `.entry` style
+ * class.
+ */
+export const AdwEntryRow = "AdwEntryRow";
+/**
+ * A [class@Gtk.ListBoxRow] used to reveal widgets.
+ *
+ *
+ *
+ * The `AdwExpanderRow` widget allows the user to reveal or hide widgets below
+ * it. It also allows the user to enable the expansion of the row, allowing to
+ * disable all that the row contains.
+ *
+ * ## AdwExpanderRow as GtkBuildable
+ *
+ * The `AdwExpanderRow` implementation of the [iface@Gtk.Buildable] interface
+ * supports adding a child as an suffix widget by specifying “suffix” as the
+ * “type” attribute of a `<child>` element.
+ *
+ * It also supports adding it as a prefix widget by specifying “prefix” as the
+ * “type” attribute of a `<child>` element.
+ *
+ * ## CSS nodes
+ *
+ * `AdwExpanderRow` has a main CSS node with name `row` and the `.expander`
+ * style class. It has the `.empty` style class when it contains no children.
+ *
+ * It contains the subnodes `row.header` for its main embedded row,
+ * `list.nested` for the list it can expand, and `image.expander-row-arrow` for
+ * its arrow.
+ *
+ * ## Style classes
+ *
+ * `AdwExpanderRow` can use the `.`
+ * style class to emphasize the row subtitle instead of the row title, which is
+ * useful for displaying read-only properties.
+ *
+ * When used together with the `.monospace` style class, only the subtitle
+ * becomes monospace, not the title or any extra widgets.
+ */
+export const AdwExpanderRow = "AdwExpanderRow";
+/**
+ * An adaptive container acting like a box or an overlay.
+ *
+ *
+ *
+ *
+ * The `AdwFlap` widget can display its children like a [class@Gtk.Box] does or
+ * like a [class@Gtk.Overlay] does, according to the
+ * [property@Flap:fold-policy] value.
+ *
+ * `AdwFlap` has at most three children: [property@Flap:content],
+ * [property@Flap:flap] and [property@Flap:separator]. Content is the primary
+ * child, flap is displayed next to it when unfolded, or overlays it when
+ * folded. Flap can be shown or hidden by changing the
+ * [property@Flap:reveal-flap] value, as well as via swipe gestures if
+ * [property@Flap:swipe-to-open] and/or [property@Flap:swipe-to-close] are set
+ * to `TRUE`.
+ *
+ * Optionally, a separator can be provided, which would be displayed between
+ * the content and the flap when there's no shadow to separate them, depending
+ * on the transition type.
+ *
+ * [property@Flap:flap] is transparent by default; add the
+ * `.background` style class to it if this is
+ * unwanted.
+ *
+ * If [property@Flap:modal] is set to `TRUE`, content becomes completely
+ * inaccessible when the flap is revealed while folded.
+ *
+ * The position of the flap and separator children relative to the content is
+ * determined by orientation, as well as the [property@Flap:flap-position]
+ * value.
+ *
+ * Folding the flap will automatically hide the flap widget, and unfolding it
+ * will automatically reveal it. If this behavior is not desired, the
+ * [property@Flap:locked] property can be used to override it.
+ *
+ * Common use cases include sidebars, header bars that need to be able to
+ * overlap the window content (for example, in fullscreen mode) and bottom
+ * sheets.
+ *
+ * ## AdwFlap as GtkBuildable
+ *
+ * The `AdwFlap` implementation of the [iface@Gtk.Buildable] interface supports
+ * setting the flap child by specifying “flap” as the “type” attribute of a
+ * ``<child>`` element, and separator by specifying “separator”. Specifying
+ * “content” child type or omitting it results in setting the content child.
+ *
+ * ## CSS nodes
+ *
+ * `AdwFlap` has a single CSS node with name `flap`. The node will get the style
+ * classes `.folded` when it is folded, and `.unfolded` when it's not.
+ */
+export const AdwFlap = {
+    Root: "AdwFlap.Root",
+    Content: "AdwFlap.Content",
+    Flap: "AdwFlap.Flap",
+    Separator: "AdwFlap.Separator",
+};
+/**
+ * A title bar widget.
+ *
+ *
+ *
+ * `AdwHeaderBar` is similar to [class@Gtk.HeaderBar], but provides additional
+ * features compared to it. Refer to `GtkHeaderBar` for details. It is typically
+ * used as a top bar within [class@ToolbarView].
+ *
+ * ## Dialog Integration
+ *
+ * When placed inside an [class@Dialog], `AdwHeaderBar` will display the dialog
+ * title instead of window title. It will also adjust the decoration layout to
+ * ensure it always has a close button and nothing else. Set
+ * [property@HeaderBar:show-start-title-buttons] and
+ * [property@HeaderBar:show-end-title-buttons] to `FALSE` to remove it if it's
+ * unwanted.
+ *
+ * ## Navigation View Integration
+ *
+ * When placed inside an [class@NavigationPage], `AdwHeaderBar` will display the
+ * page title instead of window title.
+ *
+ * When used together with [class@NavigationView] or [class@NavigationSplitView],
+ * it will also display a back button that can be used to go back to the previous
+ * page. The button also has a context menu, allowing to pop multiple pages at
+ * once, potentially across multiple navigation views.
+ *
+ * Set [property@HeaderBar:show-back-button] to `FALSE` to disable this behavior
+ * in rare scenarios where it's unwanted.
+ *
+ * ## Split View Integration
+ *
+ * When placed inside [class@NavigationSplitView] or [class@OverlaySplitView],
+ * `AdwHeaderBar` will automatically hide the title buttons other than at the
+ * edges of the window.
+ *
+ * ## Bottom Sheet Integration
+ *
+ * When played inside [class@BottomSheet], `AdwHeaderBar` will not show the title
+ * unless [property@BottomSheet:show-drag-handle] is set to `FALSE`, regardless
+ * of [property@HeaderBar:show-title]. This only applies to the default title,
+ * titles set with [property@HeaderBar:title-widget] will still be shown.
+ *
+ * ## Centering Policy
+ *
+ * [property@HeaderBar:centering-policy] allows to enforce strict centering of
+ * the title widget. This can be useful for entries inside [class@Clamp].
+ *
+ * ## Title Buttons
+ *
+ * Unlike `GtkHeaderBar`, `AdwHeaderBar` allows to toggle title button
+ * visibility for each side individually, using the
+ * [property@HeaderBar:show-start-title-buttons] and
+ * [property@HeaderBar:show-end-title-buttons] properties.
+ *
+ * ## CSS nodes
+ *
+ * ```
+ * headerbar
+ * ╰── windowhandle
+ * ╰── box
+ * ├── widget
+ * │   ╰── box.start
+ * │       ├── windowcontrols.start
+ * │       ├── widget
+ * │       │   ╰── [button.back]
+ * │       ╰── [other children]
+ * ├── widget
+ * │   ╰── [Title Widget]
+ * ╰── widget
+ * ╰── box.end
+ * ├── [other children]
+ * ╰── windowcontrols.end
+ * ```
+ *
+ * `AdwHeaderBar`'s CSS node is called `headerbar`. It contains a `windowhandle`
+ * subnode, which contains a `box` subnode, which contains three `widget`
+ * subnodes at the start, center and end of the header bar. The start and end
+ * subnodes contain a `box` subnode with the `.start` and `.end` style classes
+ * respectively, and the center node contains a node that represents the title.
+ *
+ * Each of the boxes contains a `windowcontrols` subnode, see
+ * [class@Gtk.WindowControls] for details, as well as other children.
+ *
+ * When [property@HeaderBar:show-back-button] is `TRUE`, the start box also
+ * contains a node with the name `widget` that contains a node with the name
+ * `button` and `.back` style class.
+ *
+ * ## Accessibility
+ *
+ * `AdwHeaderBar` uses the `GTK_ACCESSIBLE_ROLE_GROUP` role.
+ */
+export const AdwHeaderBar = {
+    Root: "AdwHeaderBar.Root",
+    TitleWidget: "AdwHeaderBar.TitleWidget",
+};
+/**
+ * A view switcher that uses a toggle group.
+ *
+ *
+ *
+ * A view switcher showing pages of an [class@ViewStack] within an
+ * [class@ToggleGroup], similar to [class@ViewSwitcher].
+ *
+ * The toggles can display either an icon, a label or both. Use the
+ * [property@InlineViewSwitcher:display-mode] to control this.
+ *
+ *
+ *
+ * ## CSS nodes
+ *
+ * `AdwInlineViewSwitcher` has a single CSS node with the name
+ * `inline-view-switcher`.
+ *
+ * ## Style classes
+ *
+ * Like `AdwToggleGroup`, it can accept the `.flat`
+ * and `.round` style classes.
+ *
+ *
+ *
+ * ## Accessibility
+ *
+ * The internal toggle group uses the `GTK_ACCESSIBLE_ROLE_TAB_LIST` role. Its
+ * toggles use the `GTK_ACCESSIBLE_ROLE_TAB` role.
+ */
+export const AdwInlineViewSwitcher = "AdwInlineViewSwitcher";
+/**
+ * A child slot within [class@Layout].
+ *
+ * While it contains a layout child, the [property@Gtk.Widget:visible] property
+ * of the slot is updated to match that of the layout child.
+ *
+ * See [class@MultiLayoutView].
+ */
+export const AdwLayoutSlot = "AdwLayoutSlot";
+/**
+ * An adaptive container acting like a box or a stack.
+ *
+ *
+ *
+ *
+ * The `AdwLeaflet` widget can display its children like a [class@Gtk.Box] does
+ * or like a [class@Gtk.Stack] does, adapting to size changes by switching
+ * between the two modes.
+ *
+ * When there is enough space the children are displayed side by side, otherwise
+ * only one is displayed and the leaflet is said to be “folded”.
+ * The threshold is dictated by the preferred minimum sizes of the children.
+ * When a leaflet is folded, the children can be navigated using swipe gestures.
+ *
+ * The “over” and “under” transition types stack the children one on top of the
+ * other, while the “slide” transition puts the children side by side. While
+ * navigating to a child on the side or below can be performed by swiping the
+ * current child away, navigating to an upper child requires dragging it from
+ * the edge where it resides. This doesn't affect non-dragging swipes.
+ *
+ * ## CSS nodes
+ *
+ * `AdwLeaflet` has a single CSS node with name `leaflet`. The node will get the
+ * style classes `.folded` when it is folded, `.unfolded` when it's not, or none
+ * if it hasn't computed its fold yet.
+ */
+export const AdwLeaflet = {
+    Root: "AdwLeaflet.Root",
+    VisibleChild: "AdwLeaflet.VisibleChild",
+};
+/**
+ * A dialog presenting a message or a question.
+ *
+ *
+ *
+ * Message dialogs have a heading, a body, an optional child widget, and one or
+ * multiple responses, each presented as a button.
+ *
+ * Each response has a unique string ID, and a button label. Additionally, each
+ * response can be enabled or disabled, and can have a suggested or destructive
+ * appearance.
+ *
+ * When one of the responses is activated, or the dialog is closed, the
+ * [signal@MessageDialog::response] signal will be emitted. This signal is
+ * detailed, and the detail, as well as the `response` parameter will be set to
+ * the ID of the activated response, or to the value of the
+ * [property@MessageDialog:close-response] property if the dialog had been
+ * closed without activating any of the responses.
+ *
+ * Response buttons can be presented horizontally or vertically depending on
+ * available space.
+ *
+ * When a response is activated, `AdwMessageDialog` is closed automatically.
+ *
+ * An example of using a message dialog:
+ *
+ * ```c
+ * GtkWidget *dialog;
+ *
+ * dialog = adw_message_dialog_new (parent, _("Replace File?"), NULL);
+ *
+ * adw_message_dialog_format_body (ADW_MESSAGE_DIALOG (dialog),
+ * _("A file named “%s” already exists. Do you want to replace it?"),
+ * filename);
+ *
+ * adw_message_dialog_add_responses (ADW_MESSAGE_DIALOG (dialog),
+ * "cancel",  _("_Cancel"),
+ * "replace", _("_Replace"),
+ * NULL);
+ *
+ * adw_message_dialog_set_response_appearance (ADW_MESSAGE_DIALOG (dialog), "replace", ADW_RESPONSE_DESTRUCTIVE);
+ *
+ * adw_message_dialog_set_default_response (ADW_MESSAGE_DIALOG (dialog), "cancel");
+ * adw_message_dialog_set_close_response (ADW_MESSAGE_DIALOG (dialog), "cancel");
+ *
+ * g_signal_connect (dialog, "response", G_CALLBACK (response_cb), self);
+ *
+ * gtk_window_present (GTK_WINDOW (dialog));
+ * ```
+ *
+ * ## Async API
+ *
+ * `AdwMessageDialog` can also be used via the [method@MessageDialog.choose]
+ * method. This API follows the GIO async pattern, for example:
+ *
+ * ```c
+ * static void
+ * dialog_cb (AdwMessageDialog *dialog,
+ * GAsyncResult     *result,
+ * MyWindow         *self)
+ * {
+ * const char *response = adw_message_dialog_choose_finish (dialog, result);
+ *
+ * // ...
+ * }
+ *
+ * static void
+ * show_dialog (MyWindow *self)
+ * {
+ * GtkWidget *dialog;
+ *
+ * dialog = adw_message_dialog_new (GTK_WINDOW (self), _("Replace File?"), NULL);
+ *
+ * adw_message_dialog_format_body (ADW_MESSAGE_DIALOG (dialog),
+ * _("A file named “%s” already exists. Do you want to replace it?"),
+ * filename);
+ *
+ * adw_message_dialog_add_responses (ADW_MESSAGE_DIALOG (dialog),
+ * "cancel",  _("_Cancel"),
+ * "replace", _("_Replace"),
+ * NULL);
+ *
+ * adw_message_dialog_set_response_appearance (ADW_MESSAGE_DIALOG (dialog), "replace", ADW_RESPONSE_DESTRUCTIVE);
+ *
+ * adw_message_dialog_set_default_response (ADW_MESSAGE_DIALOG (dialog), "cancel");
+ * adw_message_dialog_set_close_response (ADW_MESSAGE_DIALOG (dialog), "cancel");
+ *
+ * adw_message_dialog_choose (ADW_MESSAGE_DIALOG (dialog), NULL, (GAsyncReadyCallback) dialog_cb, self);
+ * }
+ * ```
+ *
+ * ## AdwMessageDialog as GtkBuildable
+ *
+ * `AdwMessageDialog` supports adding responses in UI definitions by via the
+ * `<responses>` element that may contain multiple `<response>` elements, each
+ * representing a response.
+ *
+ * Each of the `<response>` elements must have the `id` attribute specifying the
+ * response ID. The contents of the element are used as the response label.
+ *
+ * Response labels can be translated with the usual `translatable`, `context`
+ * and `comments` attributes.
+ *
+ * The `<response>` elements can also have `enabled` and/or `appearance`
+ * attributes. See [method@MessageDialog.set_response_enabled] and
+ * [method@MessageDialog.set_response_appearance] for details.
+ *
+ * Example of an `AdwMessageDialog` UI definition:
+ *
+ * ```xml
+ * <object class="AdwMessageDialog" id="dialog">
+ * <property name="heading" translatable="yes">Save Changes?`</property>`
+ * <property name="body" translatable="yes">Open documents contain unsaved changes. Changes which are not saved will be permanently lost.`</property>`
+ * <property name="default-response">save`</property>`
+ * <property name="close-response">cancel`</property>`
+ * <signal name="response" handler="response_cb"/>
+ * <responses>
+ * <response id="cancel" translatable="yes">_Cancel</response>
+ * <response id="discard" translatable="yes" appearance="destructive">_Discard</response>
+ * <response id="save" translatable="yes" appearance="suggested" enabled="false">_Save</response>
+ * </responses>
+ * `</object>`
+ * ```
+ *
+ * ## Accessibility
+ *
+ * `AdwMessageDialog` uses the `GTK_ACCESSIBLE_ROLE_DIALOG` role.
+ */
+export const AdwMessageDialog = {
+    Root: "AdwMessageDialog.Root",
+    ExtraChild: "AdwMessageDialog.ExtraChild",
+};
+/**
+ * A widget for switching between different layouts.
+ *
+ * `AdwMultiLayoutView` contains layouts and children. Each child has
+ * an ID, each layout has slots inside it, each slot also has an ID. When
+ * switching layouts, children are inserted into slots with matching IDs. The
+ * [property@Gtk.Widget:visible] property of each slot is updated to match
+ * that of the inserted child.
+ *
+ * This can be useful for rearranging children when it's difficult to do so
+ * otherwise, for example to move a child from a sidebar to a bottom bar.
+ *
+ * The currently used layout can be switched using the
+ * [property@MultiLayoutView:layout] or [property@MultiLayoutView:layout-name]
+ * properties. For example, it can be done via a [class@Adw.Breakpoint] setter
+ * to change layouts depending on the window size.
+ *
+ * ## AdwMultiLayoutView as GtkBuildable
+ *
+ * The `AdwMultiLayoutView` implementation of the [iface@Gtk.Buildable]
+ * interface supports adding layouts via ``<child>`` element with the `type`
+ * attribute omitted.
+ *
+ * It also supports setting children via `<child type="ID">`.
+ *
+ * Example of an `AdwMultiLayoutView` UI definition that can display a secondary
+ * child as either a sidebar or a bottom sheet.
+ *
+ * ```xml
+ * <object class="AdwMultiLayoutView">
+ * `<child>`
+ * <object class="AdwLayout">
+ * <property name="name">sidebar`</property>`
+ * <property name="content">
+ * <object class="AdwOverlaySplitView">
+ * <property name="sidebar">
+ * <object class="AdwLayoutSlot">
+ * <property name="id">secondary`</property>`
+ * `</object>`
+ * `</property>`
+ * <property name="content">
+ * <object class="AdwLayoutSlot">
+ * <property name="id">primary`</property>`
+ * `</object>`
+ * `</property>`
+ * `</object>`
+ * `</property>`
+ * `</object>`
+ * `</child>`
+ * `<child>`
+ * <object class="AdwLayout">
+ * <property name="name">bottom-sheet`</property>`
+ * <property name="content">
+ * <object class="AdwBottomSheet">
+ * <property name="open">True`</property>`
+ * <property name="content">
+ * <object class="AdwLayoutSlot">
+ * <property name="id">primary`</property>`
+ * `</object>`
+ * `</property>`
+ * <property name="sheet">
+ * <object class="AdwLayoutSlot">
+ * <property name="id">secondary`</property>`
+ * `</object>`
+ * `</property>`
+ * `</object>`
+ * `</property>`
+ * `</object>`
+ * `</child>`
+ * <child type="primary">
+ * <!-- ... -->
+ * `</child>`
+ * <child type="secondary">
+ * <!-- ... -->
+ * `</child>`
+ * `</object>`
+ * ```
+ *
+ * ## CSS nodes
+ *
+ * `AdwMultiLayoutView` has a single CSS node with name `multi-layout-view`.
+ */
+export const AdwMultiLayoutView = "AdwMultiLayoutView";
+/**
+ * A page within [class@NavigationView] or [class@NavigationSplitView].
+ *
+ * Each page has a child widget, a title and optionally a tag.
+ *
+ * The [signal@NavigationPage::showing], [signal@NavigationPage::shown],
+ * [signal@NavigationPage::hiding] and [signal@NavigationPage::hidden] signals
+ * can be used to track the page's visibility within its `AdwNavigationView`.
+ *
+ * ## Header Bar Integration
+ *
+ * When placed inside `AdwNavigationPage`, [class@HeaderBar] will display the
+ * page title instead of window title.
+ *
+ * When used together with [class@NavigationView], it will also display a back
+ * button that can be used to go back to the previous page. Set
+ * [property@HeaderBar:show-back-button] to `FALSE` to disable that behavior if
+ * it's unwanted.
+ *
+ * ## CSS Nodes
+ *
+ * `AdwNavigationPage` has a single CSS node with name
+ * `navigation-view-page`.
+ *
+ * ## Accessibility
+ *
+ * `AdwNavigationPage` uses the `GTK_ACCESSIBLE_ROLE_GROUP` role.
+ */
+export const AdwNavigationPage = "AdwNavigationPage";
+/**
+ * A widget presenting sidebar and content side by side or as a navigation view.
+ *
+ *
+ *
+ *
+ * `AdwNavigationSplitView` has two [class@NavigationPage] children: sidebar and
+ * content, and displays them side by side.
+ *
+ * When [property@NavigationSplitView:collapsed] is set to `TRUE`, it instead
+ * puts both children inside an [class@NavigationView]. The
+ * [property@NavigationSplitView:show-content] controls which child is visible
+ * while collapsed.
+ *
+ * See also [class@OverlaySplitView].
+ *
+ * `AdwNavigationSplitView` is typically used together with an [class@Breakpoint]
+ * setting the `collapsed` property to `TRUE` on small widths, as follows:
+ *
+ * ```xml
+ * <object class="AdwWindow">
+ * <property name="width-request">280`</property>`
+ * <property name="height-request">200`</property>`
+ * <property name="default-width">800`</property>`
+ * <property name="default-height">800`</property>`
+ * `<child>`
+ * <object class="AdwBreakpoint">
+ * <condition>max-width: 400sp</condition>
+ * <setter object="split_view" property="collapsed">True</setter>
+ * `</object>`
+ * `</child>`
+ * <property name="content">
+ * <object class="AdwNavigationSplitView" id="split_view">
+ * <property name="sidebar">
+ * <object class="AdwNavigationPage">
+ * <property name="title" translatable="yes">Sidebar`</property>`
+ * <property name="child">
+ * <!-- ... -->
+ * `</property>`
+ * `</object>`
+ * `</property>`
+ * <property name="content">
+ * <object class="AdwNavigationPage">
+ * <property name="title" translatable="yes">Content`</property>`
+ * <property name="child">
+ * <!-- ... -->
+ * `</property>`
+ * `</object>`
+ * `</property>`
+ * `</object>`
+ * `</property>`
+ * `</object>`
+ * ```
+ *
+ * ## Sizing
+ *
+ * When not collapsed, `AdwNavigationSplitView` changes the sidebar width
+ * depending on its own width.
+ *
+ * If possible, it tries to allocate a fraction of the total width, controlled
+ * with the [property@NavigationSplitView:sidebar-width-fraction] property.
+ *
+ * The sidebar also has minimum and maximum sizes, controlled with the
+ * [property@NavigationSplitView:min-sidebar-width] and
+ * [property@NavigationSplitView:max-sidebar-width] properties.
+ *
+ * The minimum and maximum sizes are using the length unit specified with the
+ * [property@NavigationSplitView:sidebar-width-unit].
+ *
+ * By default, sidebar is using 25% of the total width, with 180sp as the
+ * minimum size and 280sp as the maximum size.
+ *
+ * ## Header Bar Integration
+ *
+ * When used inside `AdwNavigationSplitView`, [class@HeaderBar] will
+ * automatically hide the window buttons in the middle.
+ *
+ * When collapsed, it also displays a back button for the content widget, as
+ * well as the page titles. See [class@NavigationView] documentation for details.
+ *
+ * ## Actions
+ *
+ * `AdwNavigationSplitView` defines the same actions as `AdwNavigationView`, but
+ * they can be used even when the split view is not collapsed:
+ *
+ * - `navigation.push` takes a string parameter specifying the tag of the page
+ * to push. If it matches the tag of the content widget, it sets
+ * [property@NavigationSplitView:show-content] to `TRUE`.
+ *
+ * - `navigation.pop` doesn't take any parameters and sets
+ * [property@NavigationSplitView:show-content] to `FALSE`.
+ *
+ * ## `AdwNavigationSplitView` as `GtkBuildable`
+ *
+ * The `AdwNavigationSplitView` implementation of the [iface@Gtk.Buildable]
+ * interface supports setting the sidebar widget by specifying “sidebar” as the
+ * “type” attribute of a ``<child>`` element, Specifying “content” child type or
+ * omitting it results in setting the content widget.
+ *
+ * ## CSS nodes
+ *
+ * `AdwNavigationSplitView` has a single CSS node with the name
+ * `navigation-split-view`.
+ *
+ * When collapsed, it contains a child node with the name `navigation-view`
+ * containing both children.
+ *
+ * ```
+ * navigation-split-view
+ * ╰── navigation-view
+ * ├── [sidebar child]
+ * ╰── [content child]
+ * ```
+ *
+ * When not collapsed, it contains two nodes with the name `widget`, one with
+ * the `.sidebar-pane` style class, the other one with `.content-view` style
+ * class, containing the sidebar and content children respectively.
+ *
+ * ```
+ * navigation-split-view
+ * ├── widget.sidebar-pane
+ * │   ╰── [sidebar child]
+ * ╰── widget.content-pane
+ * ╰── [content child]
+ * ```
+ *
+ * ## Accessibility
+ *
+ * `AdwNavigationSplitView` uses the `GTK_ACCESSIBLE_ROLE_GROUP` role.
+ */
+export const AdwNavigationSplitView = "AdwNavigationSplitView";
+/**
+ * A page-based navigation container.
+ *
+ *
+ *
+ * `AdwNavigationView` presents one child at a time, similar to
+ * [class@Gtk.Stack].
+ *
+ * `AdwNavigationView` can only contain [class@NavigationPage] children.
+ *
+ * It maintains a navigation stack that can be controlled with
+ * [method@NavigationView.push] and [method@NavigationView.pop]. The whole
+ * navigation stack can also be replaced using [method@NavigationView.replace].
+ *
+ * `AdwNavigationView` allows to manage pages statically or dynamically.
+ *
+ * Static pages can be added using the [method@NavigationView.add] method. The
+ * `AdwNavigationView` will keep a reference to these pages, but they aren't
+ * accessible to the user until [method@NavigationView.push] is called (except
+ * for the first page, which is pushed automatically). Use the
+ * [method@NavigationView.remove] method to remove them. This is useful for
+ * applications that have a small number of unique pages and just need
+ * navigation between them.
+ *
+ * Dynamic pages are automatically destroyed once they are popped off the
+ * navigation stack. To add a page like this, push it using the
+ * [method@NavigationView.push] method without calling
+ * [method@NavigationView.add] first.
+ *
+ * ## Tags
+ *
+ * Static pages, as well as any pages in the navigation stack, can be accessed
+ * by their [property@NavigationPage:tag]. For example,
+ * [method@NavigationView.push_by_tag] can be used to push a static page that's
+ * not in the navigation stack without having to keep a reference to it manually.
+ *
+ * ## Header Bar Integration
+ *
+ * When used inside `AdwNavigationView`, [class@HeaderBar] will automatically
+ * display a back button that can be used to go back to the previous page when
+ * possible. The button also has a context menu, allowing to pop multiple pages
+ * at once, potentially across multiple navigation views.
+ *
+ * Set [property@HeaderBar:show-back-button] to `FALSE` to disable this behavior
+ * in rare scenarios where it's unwanted.
+ *
+ * `AdwHeaderBar` will also display the title of the `AdwNavigationPage` it's
+ * placed into, so most applications shouldn't need to customize it at all.
+ *
+ * ## Shortcuts and Gestures
+ *
+ * `AdwNavigationView` supports the following shortcuts for going to the
+ * previous page:
+ *
+ * - `Escape` (unless [property@NavigationView:pop-on-escape] is set to
+ * `FALSE`)
+ * - `Alt`+`←`
+ * - Back mouse button
+ *
+ * Additionally, it supports interactive gestures:
+ *
+ * - One-finger swipe towards the right on touchscreens
+ * - Scrolling towards the right on touchpads (usually two-finger swipe)
+ *
+ * These gestures have transitions enabled regardless of the
+ * [property@NavigationView:animate-transitions] value.
+ *
+ * Applications can also enable shortcuts for pushing another page onto the
+ * navigation stack via connecting to the [signal@NavigationView::get-next-page]
+ * signal, in that case the following shortcuts are supported:
+ *
+ * - `Alt`+`→`
+ * - Forward mouse button
+ * - Swipe/scrolling towards the left
+ *
+ * For right-to-left locales, the gestures and shortcuts are reversed.
+ *
+ * [property@NavigationPage:can-pop] can be used to disable them, along with the
+ * header bar back buttons.
+ *
+ * ## Actions
+ *
+ * `AdwNavigationView` defines actions for controlling the navigation stack.
+ * actions for controlling the navigation stack:
+ *
+ * - `navigation.push` takes a string parameter specifying the tag of the page to
+ * push, and is equivalent to calling [method@NavigationView.push_by_tag].
+ *
+ * - `navigation.pop` doesn't take any parameters and pops the current page from
+ * the navigation stack, equivalent to calling [method@NavigationView.pop].
+ *
+ * ## `AdwNavigationView` as `GtkBuildable`
+ *
+ * `AdwNavigationView` allows to add pages as children, equivalent to using the
+ * [method@NavigationView.add] method.
+ *
+ * Example of an `AdwNavigationView` UI definition:
+ *
+ * ```xml
+ * <object class="AdwNavigationView">
+ * `<child>`
+ * <object class="AdwNavigationPage">
+ * <property name="title" translatable="yes">Page 1`</property>`
+ * <property name="child">
+ * <object class="AdwToolbarView">
+ * <child type="top">
+ * <object class="AdwHeaderBar"/>
+ * `</child>`
+ * <property name="content">
+ * <object class="GtkButton">
+ * <property name="label" translatable="yes">Open Page 2`</property>`
+ * <property name="halign">center`</property>`
+ * <property name="valign">center`</property>`
+ * <property name="action-name">navigation.push`</property>`
+ * <property name="action-target">'page-2'`</property>`
+ * <style>
+ * <class name="pill"/>
+ * </style>
+ * `</object>`
+ * `</property>`
+ * `</object>`
+ * `</property>`
+ * `</object>`
+ * `</child>`
+ * `<child>`
+ * <object class="AdwNavigationPage">
+ * <property name="title" translatable="yes">Page 2`</property>`
+ * <property name="tag">page-2`</property>`
+ * <property name="child">
+ * <object class="AdwToolbarView">
+ * <child type="top">
+ * <object class="AdwHeaderBar"/>
+ * `</child>`
+ * <property name="content">
+ * <!-- ... -->
+ * `</property>`
+ * `</object>`
+ * `</property>`
+ * `</object>`
+ * `</child>`
+ * `</object>`
+ * ```
+ *
+ *
+ *
+ * ## CSS nodes
+ *
+ * `AdwNavigationView` has a single CSS node with the name `navigation-view`.
+ *
+ * ## Accessibility
+ *
+ * `AdwNavigationView` uses the `GTK_ACCESSIBLE_ROLE_GROUP` role.
+ */
+export const AdwNavigationView = "AdwNavigationView";
+/**
+ * A widget presenting sidebar and content side by side or as an overlay.
+ *
+ *
+ *
+ *
+ * `AdwOverlaySplitView` has two children: sidebar and content, and displays
+ * them side by side.
+ *
+ * When [property@OverlaySplitView:collapsed] is set to `TRUE`, the sidebar is
+ * instead shown as an overlay above the content widget.
+ *
+ * The sidebar can be hidden or shown using the
+ * [property@OverlaySplitView:show-sidebar] property.
+ *
+ * Sidebar can be displayed before or after the content, this can be controlled
+ * with the [property@OverlaySplitView:sidebar-position] property.
+ *
+ * Collapsing the split view automatically hides the sidebar widget, and
+ * uncollapsing it shows the sidebar. If this behavior is not desired, the
+ * [property@OverlaySplitView:pin-sidebar] property can be used to override it.
+ *
+ * `AdwOverlaySplitView` supports an edge swipe gesture for showing the sidebar,
+ * and a swipe from the sidebar for hiding it. Gestures are only supported on
+ * touchscreen, but not touchpad. Gestures can be controlled with the
+ * [property@OverlaySplitView:enable-show-gesture] and
+ * [property@OverlaySplitView:enable-hide-gesture] properties.
+ *
+ * See also [class@NavigationSplitView].
+ *
+ * `AdwOverlaySplitView` is typically used together with an [class@Breakpoint]
+ * setting the `collapsed` property to `TRUE` on small widths, as follows:
+ *
+ * ```xml
+ * <object class="AdwWindow">
+ * <property name="default-width">800`</property>`
+ * <property name="default-height">800`</property>`
+ * `<child>`
+ * <object class="AdwBreakpoint">
+ * <condition>max-width: 400sp</condition>
+ * <setter object="split_view" property="collapsed">True</setter>
+ * `</object>`
+ * `</child>`
+ * <property name="content">
+ * <object class="AdwOverlaySplitView" id="split_view">
+ * <property name="sidebar">
+ * <!-- ... -->
+ * `</property>`
+ * <property name="content">
+ * <!-- ... -->
+ * `</property>`
+ * `</object>`
+ * `</property>`
+ * `</object>`
+ * ```
+ *
+ * `AdwOverlaySplitView` is often used for implementing the
+ * utility pane
+ * pattern.
+ *
+ * ## Sizing
+ *
+ * When not collapsed, `AdwOverlaySplitView` changes the sidebar width
+ * depending on its own width.
+ *
+ * If possible, it tries to allocate a fraction of the total width, controlled
+ * with the [property@OverlaySplitView:sidebar-width-fraction] property.
+ *
+ * The sidebar also has minimum and maximum sizes, controlled with the
+ * [property@OverlaySplitView:min-sidebar-width] and
+ * [property@OverlaySplitView:max-sidebar-width] properties.
+ *
+ * The minimum and maximum sizes are using the length unit specified with the
+ * [property@OverlaySplitView:sidebar-width-unit].
+ *
+ * By default, sidebar is using 25% of the total width, with 180sp as the
+ * minimum size and 280sp as the maximum size.
+ *
+ * When collapsed, the preferred width fraction is ignored and the sidebar uses
+ * [property@OverlaySplitView:max-sidebar-width] when possible.
+ *
+ * ## Header Bar Integration
+ *
+ * When used inside `AdwOverlaySplitView`, [class@HeaderBar] will automatically
+ * hide the window buttons in the middle.
+ *
+ * ## `AdwOverlaySplitView` as `GtkBuildable`
+ *
+ * The `AdwOverlaySplitView` implementation of the [iface@Gtk.Buildable]
+ * interface supports setting the sidebar widget by specifying “sidebar” as the
+ * “type” attribute of a ``<child>`` element, Specifying “content” child type or
+ * omitting it results in setting the content widget.
+ *
+ * ## CSS nodes
+ *
+ * `AdwOverlaySplitView` has a single CSS node with the name
+ * `overlay-split-view`.
+ *
+ * It contains two nodes with the name `widget`, containing the sidebar and
+ * content children.
+ *
+ * When not collapsed, they have the `.sidebar-view` and `.content-view` style
+ * classes respectively.
+ *
+ * ```
+ * overlay-split-view
+ * ├── widget.sidebar-pane
+ * │   ╰── [sidebar child]
+ * ╰── widget.content-pane
+ * ╰── [content child]
+ * ```
+ *
+ * When collapsed, the one containing the sidebar child has the `.background`
+ * style class and the other one has no style classes.
+ *
+ * ```
+ * overlay-split-view
+ * ├── widget.background
+ * │   ╰── [sidebar child]
+ * ╰── widget
+ * ╰── [content child]
+ * ```
+ *
+ * ## Accessibility
+ *
+ * `AdwOverlaySplitView` uses the `GTK_ACCESSIBLE_ROLE_GROUP` role.
+ */
+export const AdwOverlaySplitView = {
+    Root: "AdwOverlaySplitView.Root",
+    Content: "AdwOverlaySplitView.Content",
+    Sidebar: "AdwOverlaySplitView.Sidebar",
+};
+/**
+ * A [class@EntryRow] tailored for entering secrets.
+ *
+ *
+ *
+ * It does not show its contents in clear text, does not allow to copy it to the
+ * clipboard, and shows a warning when Caps Lock is engaged. If the underlying
+ * platform allows it, `AdwPasswordEntryRow` will also place the text in a
+ * non-pageable memory area, to avoid it being written out to disk by the
+ * operating system.
+ *
+ * It offer a way to reveal the contents in clear text.
+ *
+ * ## CSS Nodes
+ *
+ * `AdwPasswordEntryRow` has a single CSS node with name `row` that carries
+ * `.entry` and `.password` style classes.
+ */
+export const AdwPasswordEntryRow = "AdwPasswordEntryRow";
+/**
+ * A dialog showing application's preferences.
+ *
+ *
+ *
+ * The `AdwPreferencesDialog` widget presents an application's preferences
+ * gathered into pages and groups. The preferences are searchable by the user.
+ *
+ * ## Actions
+ *
+ * `AdwPrefencesDialog` defines the `navigation.pop` action, it doesn't take any
+ * parameters and pops the current subpage from the navigation stack, equivalent
+ * to calling [method@PreferencesDialog.pop_subpage].
+ *
+ * ## CSS nodes
+ *
+ * `AdwPreferencesDialog` has a main CSS node with the name `dialog` and the
+ * style class `.preferences`.
+ */
+export const AdwPreferencesDialog = {
+    Root: "AdwPreferencesDialog.Root",
+    VisiblePage: "AdwPreferencesDialog.VisiblePage",
+};
+/**
+ * A group of preference rows.
+ *
+ *
+ *
+ * An `AdwPreferencesGroup` represents a group or tightly related preferences,
+ * which in turn are represented by [class@PreferencesRow].
+ *
+ * To summarize the role of the preferences it gathers, a group can have both a
+ * title and a description. The title will be used by [class@PreferencesDialog]
+ * to let the user look for a preference.
+ *
+ * The [property@PreferencesGroup:separate-rows] property can be used to
+ * separate the rows within the group, same as when using the
+ * `.boxed-list-separate` style class
+ * instead of `.boxed-list`.
+ *
+ * ## AdwPreferencesGroup as GtkBuildable
+ *
+ * The `AdwPreferencesGroup` implementation of the [iface@Gtk.Buildable] interface
+ * supports adding [class@PreferencesRow]s to the list by omitting "type". If "type"
+ * is omitted and the widget isn't a [class@PreferencesRow] the child is added to
+ * a box below the list.
+ *
+ * When the "type" attribute of a child is `header-suffix`, the child
+ * is set as the suffix on the end of the title and description.
+ *
+ * ## CSS nodes
+ *
+ * `AdwPreferencesGroup` has a single CSS node with name `preferencesgroup`.
+ *
+ * ## Accessibility
+ *
+ * `AdwPreferencesGroup` uses the `GTK_ACCESSIBLE_ROLE_GROUP` role.
+ */
+export const AdwPreferencesGroup = {
+    Root: "AdwPreferencesGroup.Root",
+    HeaderSuffix: "AdwPreferencesGroup.HeaderSuffix",
+};
+/**
+ * A page from [class@PreferencesDialog].
+ *
+ *
+ *
+ * The `AdwPreferencesPage` widget gathers preferences groups into a single page
+ * of a preferences window.
+ *
+ * ## CSS nodes
+ *
+ * `AdwPreferencesPage` has a single CSS node with name `preferencespage`.
+ *
+ * ## Accessibility
+ *
+ * `AdwPreferencesPage` uses the `GTK_ACCESSIBLE_ROLE_GROUP` role.
+ */
+export const AdwPreferencesPage = "AdwPreferencesPage";
+/**
+ * A [class@Gtk.ListBoxRow] used to present preferences.
+ *
+ * The `AdwPreferencesRow` widget has a title that [class@PreferencesDialog]
+ * will use to let the user look for a preference. It doesn't present the title
+ * in any way and lets you present the preference as you please.
+ *
+ * [class@ActionRow] and its derivatives are convenient to use as preference
+ * rows as they take care of presenting the preference's title while letting you
+ * compose the inputs of the preference around it.
+ */
+export const AdwPreferencesRow = "AdwPreferencesRow";
+/**
+ * A window to present an application's preferences.
+ *
+ *
+ *
+ * The `AdwPreferencesWindow` widget presents an application's preferences
+ * gathered into pages and groups. The preferences are searchable by the user.
+ *
+ * ## CSS nodes
+ *
+ * `AdwPreferencesWindow` has a main CSS node with the name `window` and the
+ * style class `.preferences`.
+ */
+export const AdwPreferencesWindow = {
+    Root: "AdwPreferencesWindow.Root",
+    VisiblePage: "AdwPreferencesWindow.VisiblePage",
+};
+/**
+ * A widget that displays a keyboard shortcut.
+ *
+ *
+ *
+ * The shown shortcut can be set using the [property@ShortcutLabel:accelerator]
+ * property.
+ *
+ * Optionally, if no shortcut is set, `AdwShortcutLabel` will display a
+ * placeholder set with the [property@ShortcutLabel:disabled-text] property.
+ *
+ * The following types of shortcuts can be displayed:
+ *
+ * - A single shortcut in [func@Gtk.accelerator_parse] format, e.g. `<Control>C`:
+ *
+ *
+ *
+ * - Multiple alternative shortcuts, separated with spaces, e.g. `<Shift>A Home`:
+ *
+ *
+ *
+ * - A range of shortcuts, separated with `...`, e.g. `<Alt>1...9`:
+ *
+ *
+ *
+ * - Multiple keys pressed at once, separated with `&`, e.g. `Control_L&Control_R`:
+ *
+ *
+ *
+ * - Multiple shortcuts or keys, pressed sequentially, separated with `+`, e.g. `<Control>C+<Control>X`:
+ *
+ *
+ *
+ * ::: note
+ * `<`, `>` and `&` need to be escaped as `&lt;`, `&gt;` and `&amp;` when used in UI files.
+ *
+ * ## CSS nodes
+ *
+ * `AdwShortcutLabel` has a single CSS node with name `shortcut-label`. The
+ * individual keycap labels each have the `.keycap` style class, while the
+ * labels separating them have the `.dimmed` style class.
+ *
+ * ## Accessibility
+ *
+ * `AdwShortcutLabel` uses the `GTK_ACCESSIBLE_ROLE_LABEL` role.
+ *
+ * See also: [class@ShortcutsDialog].
+ */
+export const AdwShortcutLabel = "AdwShortcutLabel";
+/**
+ * A dialog that displays application's keyboard shortcuts.
+ *
+ *
+ *
+ * Shortcuts are grouped into sections, represented by [class@ShortcutsSection]
+ * objects. Each section has one or more items, represented by
+ * [class@ShortcutsItem] objects.
+ *
+ * To add a section to the dialog, use [method@ShortcutsDialog.add], or add it
+ * as a child when using UI files.
+ *
+ * Sections without titles can be used to further subdivide each section into
+ * groups.
+ *
+ * Example of an `AdwShortcutsDialog` UI definition:
+ *
+ * ```xml
+ * <object class="AdwShortcutsDialog" id="shortcuts_dialog">
+ * `<child>`
+ * <object class="AdwShortcutsSection">
+ * <property name="title" translatable="yes">General`</property>`
+ * `<child>`
+ * <object class="AdwShortcutsItem">
+ * <property name="title" translatable="yes">Open Menu`</property>`
+ * <property name="accelerator">F10`</property>`
+ * `</object>`
+ * `</child>`
+ * `<child>`
+ * <object class="AdwShortcutsItem">
+ * <property name="title" translatable="yes">Quit`</property>`
+ * <property name="action-name">app.quit`</property>`
+ * `</object>`
+ * `</child>`
+ * `</object>`
+ * `</child>`
+ * `<child>`
+ * <object class="AdwShortcutsSection">
+ * `<child>`
+ * <object class="AdwShortcutsItem">
+ * <property name="title" translatable="yes">Move Tab Left`</property>`
+ * <property name="accelerator">&lt;Shift&gt;&lt;Ctrl&gt;Page_Up`</property>`
+ * <property name="direction">ltr`</property>`
+ * `</object>`
+ * `</child>`
+ * `<child>`
+ * <object class="AdwShortcutsItem">
+ * <property name="title" translatable="yes">Move Tab Right`</property>`
+ * <property name="accelerator">&lt;Shift&gt;&lt;Ctrl&gt;Page_Down`</property>`
+ * <property name="direction">ltr`</property>`
+ * `</object>`
+ * `</child>`
+ * `<child>`
+ * <object class="AdwShortcutsItem">
+ * <property name="title" translatable="yes">Move Tab Right`</property>`
+ * <property name="accelerator">&lt;Shift&gt;&lt;Ctrl&gt;Page_Up`</property>`
+ * <property name="direction">rtl`</property>`
+ * `</object>`
+ * `</child>`
+ * `<child>`
+ * <object class="AdwShortcutsItem">
+ * <property name="title" translatable="yes">Move Tab Left`</property>`
+ * <property name="accelerator">&lt;Shift&gt;&lt;Ctrl&gt;Page_Down`</property>`
+ * <property name="direction">rtl`</property>`
+ * `</object>`
+ * `</child>`
+ * `</object>`
+ * `</child>`
+ * `</object>`
+ * ```
+ *
+ * If the `app.quit` action has the `Ctrl``Q` accelerator
+ * associated with it, the result will look as follows:
+ *
+ *
+ *
+ * The recommended way to use `AdwShortcutsDialog` is via [class@Application]'s
+ * automatic resource loading.
+ *
+ * See also: [class@ShortcutLabel].
+ */
+export const AdwShortcutsDialog = "AdwShortcutsDialog";
+/**
+ * A widget showing a loading spinner.
+ *
+ *
+ *
+ * The size of the spinner depends on the available size, never smaller than
+ * 16×16 pixels and never larger than 64×64 pixels.
+ *
+ * Use the [property@Gtk.Widget:halign] and [property@Gtk.Widget:valign]
+ * properties in combination with [property@Gtk.Widget:width-request] and
+ * [property@Gtk.Widget:height-request] for fine sizing control.
+ *
+ * For example, the following snippet shows the spinner at 48×48 pixels:
+ *
+ * ```xml
+ * <object class="AdwSpinner">
+ * <property name="halign">center`</property>`
+ * <property name="valign">center`</property>`
+ * <property name="width-request">48`</property>`
+ * <property name="height-request">48`</property>`
+ * `</object>`
+ * ```
+ *
+ * See [class@SpinnerPaintable] for cases where using a widget is impractical or
+ * impossible, such as [property@StatusPage:paintable].
+ *
+ * ## CSS nodes
+ *
+ * `AdwSpinner` has a single node with the name `image` and the style class
+ * `.spinner`.
+ *
+ * ## Accessibility
+ *
+ * `AdwSpinner` uses the [enum@Gtk.AccessibleRole.progress-bar] role.
+ */
+export const AdwSpinner = "AdwSpinner";
+/**
+ * An [class@ActionRow] with an embedded spin button.
+ *
+ *
+ *
+ * Example of an `AdwSpinRow` UI definition:
+ *
+ * ```xml
+ * <object class="AdwSpinRow">
+ * <property name="title" translatable="yes">Spin Row`</property>`
+ * <property name="adjustment">
+ * <object class="GtkAdjustment">
+ * <property name="lower">0`</property>`
+ * <property name="upper">100`</property>`
+ * <property name="value">50`</property>`
+ * <property name="page-increment">10`</property>`
+ * <property name="step-increment">1`</property>`
+ * `</object>`
+ * `</property>`
+ * `</object>`
+ * ```
+ *
+ * See [class@Gtk.SpinButton] for details.
+ *
+ * ## CSS nodes
+ *
+ * `AdwSpinRow` has the same structure as [class@ActionRow], as well as the
+ * `.spin` style class on the main node.
+ *
+ * ## Accessibility
+ *
+ * `AdwSpinRow` uses an internal `GtkSpinButton` with the
+ * `GTK_ACCESSIBLE_ROLE_SPIN_BUTTON` role.
+ */
+export const AdwSpinRow = "AdwSpinRow";
+/**
+ * A combined button and dropdown widget.
+ *
+ *
+ *
+ * `AdwSplitButton` is typically used to present a set of actions in a menu,
+ * but allow access to one of them with a single click.
+ *
+ * The API is very similar to [class@Gtk.Button] and [class@Gtk.MenuButton], see
+ * their documentation for details.
+ *
+ * ## CSS nodes
+ *
+ * ```
+ * splitbutton[.image-button][.text-button]
+ * ├── button
+ * │   ╰── <content>
+ * ├── separator
+ * ╰── menubutton
+ * ╰── button.toggle
+ * ╰── arrow
+ * ```
+ *
+ * `AdwSplitButton`'s CSS node is called `splitbutton`. It contains the css
+ * nodes: `button`, `separator`, `menubutton`. See [class@Gtk.MenuButton]
+ * documentation for the `menubutton` contents.
+ *
+ * The main CSS node will contain the `.image-button` or `.text-button` style
+ * classes matching the button contents. The nested button nodes will never
+ * contain them.
+ *
+ * ## Style classes
+ *
+ * `AdwSplitButton` can use some of the same style classes as [class@Gtk.Button]:
+ *
+ * - `.suggested-action`
+ * - `.destructive-action`
+ * - `.flat`
+ * - `.raised`
+ *
+ * Other style classes, like `.pill`, cannot be used.
+ *
+ * ## Accessibility
+ *
+ * `AdwSplitButton` uses the `GTK_ACCESSIBLE_ROLE_GROUP` role.
+ */
+export const AdwSplitButton = {
+    Root: "AdwSplitButton.Root",
+    Child: "AdwSplitButton.Child",
+    Popover: "AdwSplitButton.Popover",
+};
+/**
+ * A best fit container.
+ *
+ *
+ *
+ *
+ * The `AdwSqueezer` widget is a container which only shows the first of its
+ * children that fits in the available size. It is convenient to offer different
+ * widgets to represent the same data with different levels of detail, making
+ * the widget seem to squeeze itself to fit in the available space.
+ *
+ * Transitions between children can be animated as fades. This can be controlled
+ * with [property@Squeezer:transition-type].
+ *
+ * ## CSS nodes
+ *
+ * `AdwSqueezer` has a single CSS node with name `squeezer`.
+ */
+export const AdwSqueezer = "AdwSqueezer";
+/**
+ * A page used for empty/error states and similar use-cases.
+ *
+ *
+ *
+ * The `AdwStatusPage` widget can have an icon, a title, a description and a
+ * custom widget which is displayed below them.
+ *
+ * ## CSS nodes
+ *
+ * `AdwStatusPage` has a main CSS node with name `statuspage`.
+ *
+ * When setting an [class@SpinnerPaintable] as [property@StatusPage:paintable],
+ * the main nodes gains the `.spinner` style class for a more compact
+ * appearance.
+ *
+ * ## Style classes
+ *
+ * `AdwStatusPage` can use the
+ * `.compact` style class for when it
+ * needs to fit into a small space such a sidebar or a popover, similar to when
+ * using a spinner as the paintable.
+ */
+export const AdwStatusPage = "AdwStatusPage";
+/**
+ * A [class@Gtk.ListBoxRow] used to represent two states.
+ *
+ *
+ *
+ * The `AdwSwitchRow` widget contains a [class@Gtk.Switch] that allows the user
+ * to select between two states: "on" or "off". When activated, the row will
+ * invert its active state.
+ *
+ * The user can control the switch by activating the row or by dragging on the
+ * switch handle.
+ *
+ * See [class@Gtk.Switch] for details.
+ *
+ * Example of an `AdwSwitchRow` UI definition:
+ * ```xml
+ * <object class="AdwSwitchRow">
+ * <property name="title" translatable="yes">Switch Row`</property>`
+ * <signal name="notify::active" handler="switch_row_notify_active_cb"/>
+ * `</object>`
+ * ```
+ *
+ * The [property@SwitchRow:active] property should be connected to in order to
+ * monitor changes to the active state.
+ *
+ * ## Accessibility
+ *
+ * `AdwSwitchRow` uses the `GTK_ACCESSIBLE_ROLE_SWITCH` role.
+ */
+export const AdwSwitchRow = "AdwSwitchRow";
+/**
+ * A tab bar for [class@TabView].
+ *
+ *
+ *
+ * The `AdwTabBar` widget is a tab bar that can be used with conjunction with
+ * `AdwTabView`. It is typically used as a top bar within [class@ToolbarView].
+ *
+ * `AdwTabBar` can autohide and can optionally contain action widgets on both
+ * sides of the tabs.
+ *
+ * When there's not enough space to show all the tabs, `AdwTabBar` will scroll
+ * them. Pinned tabs always stay visible and aren't a part of the scrollable
+ * area.
+ *
+ * ## CSS nodes
+ *
+ * `AdwTabBar` has a single CSS node with name `tabbar`.
+ *
+ * ## Style classes
+ *
+ * By default `AdwTabBar` look like a part of an `AdwHeaderBar` and is intended
+ * to be used directly attached to one or used as a [class@ToolbarView] toolbar.
+ * The `.inline` style class removes its background,
+ * so that it can be used in different contexts instead.
+ */
+export const AdwTabBar = {
+    Root: "AdwTabBar.Root",
+    EndActionWidget: "AdwTabBar.EndActionWidget",
+    StartActionWidget: "AdwTabBar.StartActionWidget",
+};
+/**
+ * A button that displays the number of [class@TabView] pages.
+ *
+ *
+ *
+ * `AdwTabButton` is a button that displays the number of pages in a given
+ * `AdwTabView`, as well as whether one of the inactive pages needs attention.
+ *
+ * It's intended to be used as a visible indicator when there's no visible tab
+ * bar, typically opening an [class@TabOverview] on click, e.g. via the
+ * `overview.open` action name:
+ *
+ * ```xml
+ * <object class="AdwTabButton">
+ * <property name="view">view`</property>`
+ * <property name="action-name">overview.open`</property>`
+ * `</object>`
+ * ```
+ *
+ * ## CSS nodes
+ *
+ * `AdwTabButton` has a main CSS node with name `tabbutton`.
+ *
+ * # Accessibility
+ *
+ * `AdwTabButton` uses the `GTK_ACCESSIBLE_ROLE_BUTTON` role.
+ */
+export const AdwTabButton = "AdwTabButton";
+/**
+ * A tab overview for [class@TabView].
+ *
+ *
+ *
+ * `AdwTabOverview` is a widget that can display tabs from an `AdwTabView` in a
+ * grid.
+ *
+ * `AdwTabOverview` shows a thumbnail for each tab. By default thumbnails are
+ * static for all pages except the selected one. They can be made always live
+ * by setting [property@TabPage:live-thumbnail] to `TRUE`, or refreshed with
+ * [method@TabPage.invalidate_thumbnail] or
+ * [method@TabView.invalidate_thumbnails] otherwise.
+ *
+ * If the pages are too tall or too wide, the thumbnails will be cropped; use
+ * [property@TabPage:thumbnail-xalign] and [property@TabPage:thumbnail-yalign] to
+ * control which part of the page should be visible in this case.
+ *
+ * Pinned tabs are shown as smaller cards without thumbnails above the other
+ * tabs. Unlike in [class@TabBar], they still have titles, as well as an unpin
+ * button.
+ *
+ * `AdwTabOverview` provides search in open tabs. It searches in tab titles and
+ * tooltips, as well as [property@TabPage:keyword].
+ *
+ * If [property@TabOverview:enable-new-tab] is set to `TRUE`, a new tab button
+ * will be shown. Connect to the [signal@TabOverview::create-tab] signal to use
+ * it.
+ *
+ * [property@TabOverview:secondary-menu] can be used to provide a secondary menu
+ * for the overview. Use it to add extra actions, e.g. to open a new window or
+ * undo closed tab.
+ *
+ * `AdwTabOverview` is intended to be used as the direct child of the window,
+ * with the rest of the window contents set as the [property@TabOverview:child].
+ * The child is expected to contain an [class@TabView].
+ *
+ * `AdwTabOverview` shows window buttons by default. They can be disabled by
+ * setting [property@TabOverview:show-start-title-buttons] and/or
+ * [property@TabOverview:show-start-title-buttons] and/or
+ * [property@TabOverview:show-end-title-buttons] to `FALSE`.
+ *
+ * If search and window buttons are disabled, and secondary menu is not set, the
+ * header bar will be hidden.
+ *
+ * ## Actions
+ *
+ * `AdwTabOverview` defines the `overview.open` and `overview.close` actions for
+ * opening and closing itself. They can be convenient when used together with
+ * [class@TabButton].
+ *
+ * ## CSS nodes
+ *
+ * `AdwTabOverview` has a single CSS node with name `taboverview`.
+ */
+export const AdwTabOverview = "AdwTabOverview";
+/**
+ * A dynamic tabbed container.
+ *
+ * `AdwTabView` is a container which shows one child at a time. While it
+ * provides keyboard shortcuts for switching between pages, it does not provide
+ * a visible tab switcher and relies on external widgets for that, such as
+ * [class@TabBar], [class@TabOverview] and [class@TabButton].
+ *
+ * `AdwTabView` maintains a [class@TabPage] object for each page, which holds
+ * additional per-page properties. You can obtain the `AdwTabPage` for a page
+ * with [method@TabView.get_page], and as the return value for
+ * [method@TabView.append] and other functions for adding children.
+ *
+ * `AdwTabView` only aims to be useful for dynamic tabs in multi-window
+ * document-based applications, such as web browsers, file managers, text
+ * editors or terminals. It does not aim to replace [class@Gtk.Notebook] for use
+ * cases such as tabbed dialogs.
+ *
+ * As such, it does not support disabling page reordering or detaching.
+ *
+ * `AdwTabView` adds a number of global page switching and reordering shortcuts.
+ * The [property@TabView:shortcuts] property can be used to manage them.
+ *
+ * See [flags@TabViewShortcuts] for the list of the available shortcuts. All of
+ * the shortcuts are enabled by default.
+ *
+ * [method@TabView.add_shortcuts] and [method@TabView.remove_shortcuts] can be
+ * used to manage shortcuts in a convenient way, for example:
+ *
+ * ```c
+ * adw_tab_view_remove_shortcuts (view, ADW_TAB_VIEW_SHORTCUT_CONTROL_HOME |
+ * ADW_TAB_VIEW_SHORTCUT_CONTROL_END);
+ * ```
+ *
+ * ## CSS nodes
+ *
+ * `AdwTabView` has a main CSS node with the name `tabview`.
+ *
+ * ## Accessibility
+ *
+ * `AdwTabView` uses the `GTK_ACCESSIBLE_ROLE_TAB_PANEL` for the tab pages which
+ * are the accessible parent objects of the child widgets.
+ */
+export const AdwTabView = "AdwTabView";
+/**
+ * A widget showing toasts above its content.
+ *
+ *
+ *
+ * Much like [class@Gtk.Overlay], `AdwToastOverlay` is a container with a single
+ * main child, on top of which it can display a [class@Toast], overlaid.
+ * Toasts can be shown with [method@ToastOverlay.add_toast].
+ *
+ * Use [method@ToastOverlay.dismiss_all] to dismiss all toasts at once, or
+ * [method@Toast.dismiss] to dismiss a single toast.
+ *
+ * See [class@Toast] for details.
+ *
+ * ## CSS nodes
+ *
+ * ```
+ * toastoverlay
+ * ├── [child]
+ * ├── toast
+ * ┊   ├── widget
+ * ┊   │   ├── [label.heading]
+ * │   ╰── [custom title]
+ * ├── [button]
+ * ╰── button.circular.flat
+ * ```
+ *
+ * `AdwToastOverlay`'s CSS node is called `toastoverlay`. It contains the child,
+ * as well as zero or more `toast` subnodes.
+ *
+ * Each of the `toast` nodes contains a `widget` subnode, optionally a `button`
+ * subnode, and another `button` subnode with `.circular` and `.flat` style
+ * classes.
+ *
+ * The `widget` subnode contains a `label` subnode with the `.heading` style
+ * class, or a custom widget provided by the application.
+ *
+ * ## Accessibility
+ *
+ * `AdwToastOverlay` uses the [enum@Gtk.AccessibleRole.GROUP] role.
+ */
+export const AdwToastOverlay = "AdwToastOverlay";
+/**
+ * A group of exclusive toggles.
+ *
+ *
+ *
+ * `AdwToggleGroup` presents a set of exclusive toggles, represented as
+ * [class@Toggle] objects. Each toggle can display an icon, a label, an icon
+ * and a label, or a custom child.
+ *
+ * Toggles are indexed by their position, with the first toggle being equivalent
+ * to 0, and so on. Use the [property@ToggleGroup:active] to get that position.
+ *
+ * Toggles can also have optional names, set via the [property@Toggle:name]
+ * property. The name of the active toggle can be accessed via the
+ * [property@ToggleGroup:active-name] property.
+ *
+ * `AdwToggle` objects can be retrieved via their index or name, using
+ * [method@ToggleGroup.get_toggle] or [method@ToggleGroup.get_toggle_by_name]
+ * respectively. `AdwToggleGroup` also provides a [iface@Gtk.SelectionModel] of
+ * its toggles via the [property@ToggleGroup:toggles] property.
+ *
+ * `AdwToggleGroup` is orientable, and the toggles can be displayed horizontally
+ * or vertically. This is mostly useful for icon-only toggles.
+ *
+ * Use the [property@ToggleGroup:homogeneous] property to make the toggles take
+ * the same size, and the [property@ToggleGroup:can-shrink] to control whether
+ * the toggles can ellipsize.
+ *
+ * Example of an `AdwToggleGroup` UI definition:
+ *
+ * ```xml
+ * <object class="AdwToggleGroup">
+ * <property name="active-name">picture`</property>`
+ * `<child>`
+ * <object class="AdwToggle">
+ * <property name="icon-name">camera-photo-symbolic`</property>`
+ * <property name="tooltip" translatable="yes">Picture Mode`</property>`
+ * <property name="name">picture`</property>`
+ * `</object>`
+ * `</child>`
+ * `<child>`
+ * <object class="AdwToggle">
+ * <property name="icon-name">camera-video-symbolic`</property>`
+ * <property name="tooltip" translatable="yes">Recording Mode`</property>`
+ * <property name="name">recording`</property>`
+ * `</object>`
+ * `</child>`
+ * `</object>`
+ * ```
+ *
+ * See also: [class@InlineViewSwitcher].
+ *
+ * ## CSS nodes
+ *
+ * `AdwToggleGroup` has a main CSS node with the name `toggle-group`.
+ *
+ * Its toggles have CSS nodes with the name `toggle`, and its separators have nodes
+ * with the name `separator`.
+ *
+ * Toggle nodes will have a different style classes depending on their content:
+ * `.text-button` for labels, `.image-button` for icons, `.image-text-button`
+ * for both or no style class for custom children.
+ *
+ * The hidden separators use the `.hidden` style class.
+ *
+ * ## Style classes
+ *
+ * `AdwToggleGroup` can use the `.flat` style class
+ * to remove its background and make it look like a group of buttons.
+ *
+ *
+ *
+ * It can also use the `.round` style class to make
+ * its toggles and the group itself rounded.
+ *
+ *
+ *
+ * They can also be combined with each other.
+ *
+ *
+ *
+ * ## Accessibility
+ *
+ * `AdwToggleGroup` uses the `GTK_ACCESSIBLE_ROLE_RADIO_GROUP` role. Its toggles
+ * use the `GTK_ACCESSIBLE_ROLE_RADIO` role.
+ */
+export const AdwToggleGroup = "AdwToggleGroup";
+/**
+ * A widget containing a page, as well as top and/or bottom bars.
+ *
+ *
+ *
+ * `AdwToolbarView` has a single content widget and one or multiple top and
+ * bottom bars, shown at the top and bottom sides respectively.
+ *
+ * Example of an `AdwToolbarView` UI definition:
+ * ```xml
+ * <object class="AdwToolbarView">
+ * <child type="top">
+ * <object class="AdwHeaderBar"/>
+ * `</child>`
+ * <property name="content">
+ * <object class="AdwPreferencesPage">
+ * <!-- ... -->
+ * `</object>`
+ * `</property>`
+ * `</object>`
+ * ```
+ *
+ * The following kinds of top and bottom bars are supported:
+ *
+ * - [class@HeaderBar]
+ * - [class@TabBar]
+ * - [class@ViewSwitcherBar]
+ * - [class@Gtk.ActionBar]
+ * - [class@Gtk.HeaderBar]
+ * - [class@Gtk.PopoverMenuBar]
+ * - [class@Gtk.SearchBar]
+ * - Any [class@Gtk.Box] or a similar widget with the
+ * `.toolbar` style class
+ *
+ * By default, top and bottom bars are flat and scrolling content has a subtle
+ * undershoot shadow, same as when using the
+ * `.undershoot-top` and
+ * `.undershoot-bottom` style
+ * classes. This works well in most cases, e.g. with [class@StatusPage] or
+ * [class@PreferencesPage], where the background at the top and bottom parts of
+ * the page is uniform. Additionally, windows with sidebars should always use
+ * this style.
+ *
+ * [property@ToolbarView:top-bar-style] and
+ * [property@ToolbarView:bottom-bar-style] properties can be used add an opaque
+ * background and a persistent shadow to top and bottom bars, this can be useful
+ * for content such as utility panes,
+ * where some elements are adjacent to the top/bottom bars, or [class@TabView],
+ * where each page can have a different background.
+ *
+ *
+ *
+ *
+ *
+ * `AdwToolbarView` ensures the top and bottom bars have consistent backdrop
+ * styles and vertical spacing. For comparison:
+ *
+ *
+ *
+ *
+ * Any top and bottom bars can also be dragged to move the window, equivalent
+ * to putting them into a [class@Gtk.WindowHandle].
+ *
+ * Content is typically place between top and bottom bars, but can also extend
+ * behind them. This is controlled with the
+ * [property@ToolbarView:extend-content-to-top-edge] and
+ * [property@ToolbarView:extend-content-to-bottom-edge] properties.
+ *
+ * Top and bottom bars can be hidden and revealed with an animation using the
+ * [property@ToolbarView:reveal-top-bars] and
+ * [property@ToolbarView:reveal-bottom-bars] properties.
+ *
+ * ## `AdwToolbarView` as `GtkBuildable`
+ *
+ * The `AdwToolbarView` implementation of the [iface@Gtk.Buildable] interface
+ * supports adding a top bar by specifying “top” as the “type” attribute of a
+ * ``<child>`` element, or adding a bottom bar by specifying “bottom”.
+ *
+ * ## Accessibility
+ *
+ * `AdwToolbarView` uses the `GTK_ACCESSIBLE_ROLE_GROUP` role.
+ */
+export const AdwToolbarView = {
+    Root: "AdwToolbarView.Root",
+    Content: "AdwToolbarView.Content",
+    Top: "AdwToolbarView.Top",
+    Bottom: "AdwToolbarView.Bottom",
+};
+/**
+ * A view container for [class@ViewSwitcher].
+ *
+ * `AdwViewStack` is a container which only shows one page at a time.
+ * It is typically used to hold an application's main views.
+ *
+ * It doesn't provide a way to transition between pages.
+ * Instead, a separate widget such as [class@ViewSwitcher] can be used with
+ * `AdwViewStack` to provide this functionality.
+ *
+ * `AdwViewStack` pages can have a title, an icon, an attention request, and a
+ * numbered badge that [class@ViewSwitcher] will use to let users identify which
+ * page is which. Set them using the [property@ViewStackPage:title],
+ * [property@ViewStackPage:icon-name],
+ * [property@ViewStackPage:needs-attention], and
+ * [property@ViewStackPage:badge-number] properties.
+ *
+ * Unlike [class@Gtk.Stack], transitions between views can only be animated via
+ * a crossfade and size changes are always interpolated. Animations are disabled
+ * by default. Use [property@ViewStack:enable-transitions] to enable them.
+ *
+ * `AdwViewStack` maintains a [class@ViewStackPage] object for each added child,
+ * which holds additional per-child properties. You obtain the
+ * [class@ViewStackPage] for a child with [method@ViewStack.get_page] and you
+ * can obtain a [iface@Gtk.SelectionModel] containing all the pages with
+ * [method@ViewStack.get_pages].
+ *
+ * ## AdwViewStack as GtkBuildable
+ *
+ * To set child-specific properties in a .ui file, create
+ * [class@ViewStackPage] objects explicitly, and set the child widget as a
+ * property on it:
+ *
+ * ```xml
+ * <object class="AdwViewStack" id="stack">
+ * `<child>`
+ * <object class="AdwViewStackPage">
+ * <property name="name">overview`</property>`
+ * <property name="title">Overview`</property>`
+ * <property name="child">
+ * <object class="AdwStatusPage">
+ * <property name="title">Welcome!`</property>`
+ * `</object>`
+ * `</property>`
+ * `</object>`
+ * `</child>`
+ * `</object>`
+ * ```
+ *
+ * ## CSS nodes
+ *
+ * `AdwViewStack` has a single CSS node named `stack`.
+ *
+ * ## Accessibility
+ *
+ * `AdwViewStack` uses the `GTK_ACCESSIBLE_ROLE_TAB_PANEL` for the stack pages
+ * which are the accessible parent objects of the child widgets.
+ */
+export const AdwViewStack = {
+    Root: "AdwViewStack.Root",
+    VisibleChild: "AdwViewStack.VisibleChild",
+};
+/**
+ * An adaptive view switcher.
+ *
+ *
+ *
+ * An adaptive view switcher designed to switch between multiple views
+ * contained in a [class@ViewStack] in a similar fashion to
+ * [class@Gtk.StackSwitcher].
+ *
+ * `AdwViewSwitcher` buttons always have an icon and a label. They can be
+ * displayed side by side, or icon on top of the label. This can be controlled
+ * via the [property@ViewSwitcher:policy] property.
+ *
+ * `AdwViewSwitcher` is intended to be used in a header bar together with
+ * [class@ViewSwitcherBar] at the bottom of the window, and a [class@Breakpoint]
+ * showing the view switcher bar on narrow sizes, while removing the view
+ * switcher from the header bar, as follows:
+ *
+ * ```xml
+ * <object class="AdwWindow">
+ * `<child>`
+ * <object class="AdwBreakpoint">
+ * <condition>max-width: 550sp</condition>
+ * <setter object="switcher_bar" property="reveal">True</setter>
+ * <setter object="header_bar" property="title-widget"/>
+ * `</object>`
+ * `</child>`
+ * <property name="content">
+ * <object class="AdwToolbarView">
+ * <child type="top">
+ * <object class="AdwHeaderBar" id="header_bar">
+ * <property name="title-widget">
+ * <object class="AdwViewSwitcher">
+ * <property name="stack">stack`</property>`
+ * <property name="policy">wide`</property>`
+ * `</object>`
+ * `</property>`
+ * `</object>`
+ * `</child>`
+ * <property name="content">
+ * <object class="AdwViewStack" id="stack"/>
+ * `</property>`
+ * <child type="bottom">
+ * <object class="AdwViewSwitcherBar" id="switcher_bar">
+ * <property name="stack">stack`</property>`
+ * `</object>`
+ * `</child>`
+ * `</object>`
+ * `</property>`
+ * `</object>`
+ * ```
+ *
+ * It's recommended to set [property@ViewSwitcher:policy] to
+ * `ADW_VIEW_SWITCHER_POLICY_WIDE` in this case.
+ *
+ * You may have to adjust the breakpoint condition for your specific pages.
+ *
+ * ## CSS nodes
+ *
+ * `AdwViewSwitcher` has a single CSS node with name `viewswitcher`. It can have
+ * the style classes `.wide` and `.narrow`, matching its policy.
+ *
+ * ## Accessibility
+ *
+ * `AdwViewSwitcher` uses the `GTK_ACCESSIBLE_ROLE_TAB_LIST` role and uses the
+ * `GTK_ACCESSIBLE_ROLE_TAB` for its buttons.
+ */
+export const AdwViewSwitcher = "AdwViewSwitcher";
+/**
+ * A view switcher action bar.
+ *
+ *
+ *
+ * An action bar letting you switch between multiple views contained in a
+ * [class@ViewStack], via an [class@ViewSwitcher]. It is designed to be put at
+ * the bottom of a window and to be revealed only on really narrow windows, e.g.
+ * on mobile phones. It can't be revealed if there are less than two pages.
+ *
+ * `AdwViewSwitcherBar` is intended to be used together with
+ * `AdwViewSwitcher` in a header bar, and a [class@Breakpoint] showing the view
+ * switcher bar on narrow sizes, while removing the view switcher from the
+ * header bar, as follows:
+ *
+ * ```xml
+ * <object class="AdwWindow">
+ * `<child>`
+ * <object class="AdwBreakpoint">
+ * <condition>max-width: 550sp</condition>
+ * <setter object="switcher_bar" property="reveal">True</setter>
+ * <setter object="header_bar" property="title-widget"/>
+ * `</object>`
+ * `</child>`
+ * <property name="content">
+ * <object class="AdwToolbarView">
+ * <child type="top">
+ * <object class="AdwHeaderBar" id="header_bar">
+ * <property name="title-widget">
+ * <object class="AdwViewSwitcher">
+ * <property name="stack">stack`</property>`
+ * <property name="policy">wide`</property>`
+ * `</object>`
+ * `</property>`
+ * `</object>`
+ * `</child>`
+ * <property name="content">
+ * <object class="AdwViewStack" id="stack"/>
+ * `</property>`
+ * <child type="bottom">
+ * <object class="AdwViewSwitcherBar" id="switcher_bar">
+ * <property name="stack">stack`</property>`
+ * `</object>`
+ * `</child>`
+ * `</object>`
+ * `</property>`
+ * `</object>`
+ * ```
+ *
+ * It's recommended to set [property@ViewSwitcher:policy] to
+ * `ADW_VIEW_SWITCHER_POLICY_WIDE` in this case.
+ *
+ * You may have to adjust the breakpoint condition for your specific pages.
+ *
+ * ## CSS nodes
+ *
+ * `AdwViewSwitcherBar` has a single CSS node with name` viewswitcherbar`.
+ */
+export const AdwViewSwitcherBar = "AdwViewSwitcherBar";
+/**
+ * A view switcher title.
+ *
+ *
+ *
+ * A widget letting you switch between multiple views contained by a
+ * [class@ViewStack] via an [class@ViewSwitcher].
+ *
+ * It is designed to be used as the title widget of a [class@HeaderBar], and
+ * will display the window's title when the window is too narrow to fit the view
+ * switcher e.g. on mobile phones, or if there are less than two views.
+ *
+ * In order to center the title in narrow windows, the header bar should have
+ * [property@HeaderBar:centering-policy] set to
+ * `ADW_CENTERING_POLICY_STRICT`.
+ *
+ * `AdwViewSwitcherTitle` is intended to be used together with
+ * [class@ViewSwitcherBar].
+ *
+ * A common use case is to bind the [property@ViewSwitcherBar:reveal] property
+ * to [property@ViewSwitcherTitle:title-visible] to automatically reveal the
+ * view switcher bar when the title label is displayed in place of the view
+ * switcher, as follows:
+ *
+ * ```xml
+ * <object class="AdwWindow">
+ * <property name="content">
+ * <object class="AdwToolbarView">
+ * <child type="top">
+ * <object class="AdwHeaderBar">
+ * <property name="centering-policy">strict`</property>`
+ * <property name="title-widget">
+ * <object class="AdwViewSwitcherTitle" id="title">
+ * <property name="stack">stack`</property>`
+ * `</object>`
+ * `</property>`
+ * `</object>`
+ * `</child>`
+ * <property name="content">
+ * <object class="AdwViewStack" id="stack"/>
+ * `</property>`
+ * <child type="bottom">
+ * <object class="AdwViewSwitcherBar">
+ * <property name="stack">stack`</property>`
+ * <binding name="reveal">
+ * <lookup name="title-visible">title</lookup>
+ * </binding>
+ * `</object>`
+ * `</child>`
+ * `</object>`
+ * `</property>`
+ * `</object>`
+ * ```
+ *
+ * ## CSS nodes
+ *
+ * `AdwViewSwitcherTitle` has a single CSS node with name `viewswitchertitle`.
+ */
+export const AdwViewSwitcherTitle = "AdwViewSwitcherTitle";
+/**
+ * A helper widget for setting a window's title and subtitle.
+ *
+ *
+ *
+ * `AdwWindowTitle` shows a title and subtitle. It's intended to be used as the
+ * title child of [class@Gtk.HeaderBar] or [class@HeaderBar].
+ *
+ * ## CSS nodes
+ *
+ * `AdwWindowTitle` has a single CSS node with name `windowtitle`.
+ */
+export const AdwWindowTitle = "AdwWindowTitle";
+/**
+ * A box-like widget that can wrap into multiple lines.
+ *
+ *
+ *
+ * `AdwWrapBox` is similar to [class@Gtk.Box], but can wrap lines when the
+ * widgets cannot fit otherwise. Unlike [class@Gtk.FlowBox], the children aren't
+ * arranged into a grid and behave more like words in a wrapping label.
+ *
+ * Like `GtkBox`, `AdwWrapBox` is orientable and has spacing:
+ *
+ * - [property@WrapBox:child-spacing] between children in the same line;
+ * - [property@WrapBox:line-spacing] between lines.
+ *
+ * ::: note
+ * Unlike `GtkBox`, `AdwWrapBox` cannot follow the CSS `border-spacing`
+ * property.
+ *
+ * Use the [property@WrapBox:natural-line-length] property to determine the
+ * layout's natural size, e.g. when using it in a [class@Gtk.Popover].
+ *
+ * Normally, a horizontal `AdwWrapBox` wraps left to right and top to bottom
+ * for left-to-right languages. Both of these directions can be reversed, using
+ * the [property@WrapBox:pack-direction] and [property@WrapBox:wrap-reverse]
+ * properties. Additionally, the alignment of each line can be controlled with
+ * the [property@WrapBox:align] property.
+ *
+ * Lines can be justified using the [property@WrapBox:justify] property, filling
+ * the entire line by either increasing child size or spacing depending on the
+ * value. Set [property@WrapBox:justify-last-line] to justify the last line as
+ * well.
+ *
+ * By default, `AdwWrapBox` wraps as soon as the previous line cannot fit any
+ * more children without shrinking them past their natural size. Set
+ * [property@WrapBox:wrap-policy] to [enum@Adw.WrapPolicy.MINIMUM] to only wrap
+ * once all the children in the previous line have been shrunk to their minimum
+ * size.
+ *
+ * To make each line take the same amount of space, set
+ * [property@WrapBox:line-homogeneous] to `TRUE`.
+ *
+ * Spacing and natural line length can scale with the text scale factor, use the
+ * [property@WrapBox:child-spacing-unit], [property@WrapBox:line-spacing-unit]
+ * and/or [property@WrapBox:natural-line-length-unit] properties to enable that
+ * behavior.
+ *
+ * See [class@WrapLayout].
+ *
+ * ## CSS nodes
+ *
+ * `AdwWrapBox` uses a single CSS node with name `wrap-box`.
+ *
+ * ## Accessibility
+ *
+ * `AdwWrapBox` uses the `GTK_ACCESSIBLE_ROLE_GROUP` role.
+ */
+export const AdwWrapBox = "AdwWrapBox";
+/**
+ * Widget for single cell of completion proposal.
+ *
+ * The `GtkSourceCompletionCell` widget provides a container to display various
+ * types of information with the completion display.
+ *
+ * Each proposal may consist of multiple cells depending on the complexity of
+ * the proposal. For example, programming language proposals may contain a cell
+ * for the "left-hand-side" of an operation along with the "typed-text" for a
+ * function name and "parameters". They may also optionally set an icon to
+ * signify the kind of result.
+ *
+ * A [iface@CompletionProvider] should implement the
+ * [vfunc@CompletionProvider.display] virtual function to control
+ * how to convert data from their [iface@CompletionProposal] to content for
+ * the `GtkSourceCompletionCell`.
+ */
+export const GtkSourceCompletionCell = {
+    Root: "GtkSourceCompletionCell.Root",
+    Widget: "GtkSourceCompletionCell.Widget",
+};
+/**
+ * Gutter object for [class@View].
+ *
+ * The `GtkSourceGutter` object represents the left or right gutter of the text
+ * view. It is used by [class@View] to draw the line numbers and
+ * [class@Mark]s that might be present on a line. By packing
+ * additional [class@GutterRenderer] objects in the gutter, you can extend the
+ * gutter with your own custom drawings.
+ *
+ * To get a `GtkSourceGutter`, use the [method@View.get_gutter] function.
+ *
+ * The gutter works very much the same way as cells rendered in a [class@Gtk.TreeView].
+ * The concept is similar, with the exception that the gutter does not have an
+ * underlying [iface@Gtk.TreeModel]. The builtin line number renderer is at position
+ * %GTK_SOURCE_VIEW_GUTTER_POSITION_LINES (-30) and the marks renderer is at
+ * %GTK_SOURCE_VIEW_GUTTER_POSITION_MARKS (-20). The gutter sorts the renderers
+ * in ascending order, from left to right. So the marks are displayed on the
+ * right of the line numbers.
+ */
+export const GtkSourceGutter = "GtkSourceGutter";
+/**
+ * Gutter cell renderer.
+ *
+ * A `GtkSourceGutterRenderer` represents a column in a [class@Gutter]. The
+ * column contains one cell for each visible line of the [class@Gtk.TextBuffer]. Due to
+ * text wrapping, a cell can thus span multiple lines of the [class@Gtk.TextView]. In
+ * this case, [enum@GutterRendererAlignmentMode] controls the alignment of
+ * the cell.
+ *
+ * The gutter renderer is a [class@Gtk.Widget] and is measured using the normal widget
+ * measurement facilities. The width of the gutter will be determined by the
+ * measurements of the gutter renderers.
+ *
+ * The width of a gutter renderer generally takes into account the entire text
+ * buffer. For instance, to display the line numbers, if the buffer contains 100
+ * lines, the gutter renderer will always set its width such as three digits can
+ * be printed, even if only the first 20 lines are shown. Another strategy is to
+ * take into account only the visible lines.  In this case, only two digits are
+ * necessary to display the line numbers of the first 20 lines. To take another
+ * example, the gutter renderer for [class@Mark]s doesn't need to take
+ * into account the text buffer to announce its width. It only depends on the
+ * icons size displayed in the gutter column.
+ *
+ * When the available size to render a cell is greater than the required size to
+ * render the cell contents, the cell contents can be aligned horizontally and
+ * vertically with [method@GutterRenderer.set_alignment_mode].
+ *
+ * The cells rendering occurs using [vfunc@Gtk.Widget.snapshot]. Implementations
+ * should use `gtk_source_gutter_renderer_get_lines()` to retrieve information
+ * about the lines to be rendered. To help with aligning content which takes
+ * into account the padding and alignment of a cell, implementations may call
+ * [method@GutterRenderer.align_cell] for a given line number with the
+ * width and height measurement of the content they width to render.
+ */
+export const GtkSourceGutterRenderer = "GtkSourceGutterRenderer";
+/**
+ * Renders a pixbuf in the gutter.
+ *
+ * A `GtkSourceGutterRendererPixbuf` can be used to render an image in a cell of
+ * [class@Gutter].
+ */
+export const GtkSourceGutterRendererPixbuf = "GtkSourceGutterRendererPixbuf";
+/**
+ * Renders text in the gutter.
+ *
+ * A `GtkSourceGutterRendererText` can be used to render text in a cell of
+ * [class@Gutter].
+ */
+export const GtkSourceGutterRendererText = "GtkSourceGutterRendererText";
+/**
+ * Display for interactive tooltips.
+ *
+ * `GtkSourceHoverDisplay` is a [class@Gtk.Widget] that may be populated with widgets
+ * to be displayed to the user in interactive tooltips. The children widgets
+ * are packed vertically using a [class@Gtk.Box].
+ *
+ * Implement the [iface@HoverProvider] interface to be notified of when
+ * to populate a `GtkSourceHoverDisplay` on behalf of the user.
+ */
+export const GtkSourceHoverDisplay = "GtkSourceHoverDisplay";
+/**
+ * Widget that displays a map for a specific [class@View].
+ *
+ * `GtkSourceMap` is a widget that maps the content of a [class@View] into
+ * a smaller view so the user can have a quick overview of the whole document.
+ *
+ * This works by connecting a [class@View] to to the `GtkSourceMap` using
+ * the [property@Map:view] property or [method@Map.set_view].
+ *
+ * `GtkSourceMap` is a [class@View] object. This means that you can add a
+ * [class@GutterRenderer] to a gutter in the same way you would for a
+ * [class@View]. One example might be a [class@GutterRenderer] that shows
+ * which lines have changed in the document.
+ *
+ * Additionally, it is desirable to match the font of the `GtkSourceMap` and
+ * the [class@View] used for editing. Therefore, [property@Map:font-desc]
+ * should be used to set the target font. You will need to adjust this to the
+ * desired font size for the map. A 1pt font generally seems to be an
+ * appropriate font size. "Monospace 1" is the default. See
+ * [method@Pango.FontDescription.set_size] for how to alter the size of an existing
+ * [struct@Pango.FontDescription].
+ *
+ * When FontConfig is available, `GtkSourceMap` will try to use a bundled
+ * "block" font to make the map more legible.
+ */
+export const GtkSourceMap = "GtkSourceMap";
+/**
+ * A button to launch a style scheme selection dialog.
+ *
+ * The `GtkSourceStyleSchemeChooserButton` is a button which displays
+ * the currently selected style scheme and allows to open a style scheme
+ * selection dialog to change the style scheme.
+ * It is suitable widget for selecting a style scheme in a preference dialog.
+ *
+ * In `GtkSourceStyleSchemeChooserButton`, a [class@StyleSchemeChooserWidget]
+ * is used to provide a dialog for selecting style schemes.
+ */
+export const GtkSourceStyleSchemeChooserButton = "GtkSourceStyleSchemeChooserButton";
+/**
+ * A widget for choosing style schemes.
+ *
+ * The `GtkSourceStyleSchemeChooserWidget` widget lets the user select a
+ * style scheme. By default, the chooser presents a predefined list
+ * of style schemes.
+ *
+ * To change the initially selected style scheme,
+ * use [method@StyleSchemeChooser.set_style_scheme].
+ * To get the selected style scheme
+ * use [method@StyleSchemeChooser.get_style_scheme].
+ */
+export const GtkSourceStyleSchemeChooserWidget = "GtkSourceStyleSchemeChooserWidget";
+/**
+ * A preview widget for [class@StyleScheme].
+ *
+ * This widget provides a convenient [class@Gtk.Widget] to preview a [class@StyleScheme].
+ *
+ * The [property@StyleSchemePreview:selected] property can be used to manage
+ * the selection state of a single preview widget.
+ */
+export const GtkSourceStyleSchemePreview = "GtkSourceStyleSchemePreview";
+/**
+ * Subclass of [class@Gtk.TextView].
+ *
+ * `GtkSourceView` is the main class of the GtkSourceView library.
+ * Use a [class@Buffer] to display text with a `GtkSourceView`.
+ *
+ * This class provides:
+ *
+ * - Show the line numbers;
+ * - Show a right margin;
+ * - Highlight the current line;
+ * - Indentation settings;
+ * - Configuration for the Home and End keyboard keys;
+ * - Configure and show line marks;
+ * - And a few other things.
+ *
+ * An easy way to test all these features is to use the test-widget mini-program
+ * provided in the GtkSourceView repository, in the tests/ directory.
+ *
+ * # GtkSourceView as GtkBuildable
+ *
+ * The GtkSourceView implementation of the [iface@Gtk.Buildable] interface exposes the
+ * [property@View:completion] object with the internal-child "completion".
+ *
+ * An example of a UI definition fragment with GtkSourceView:
+ * ```xml
+ * <object class="GtkSourceView" id="source_view">
+ * <property name="tab-width">4`</property>`
+ * <property name="auto-indent">True`</property>`
+ * <child internal-child="completion">
+ * <object class="GtkSourceCompletion">
+ * <property name="select-on-show">False`</property>`
+ * `</object>`
+ * `</child>`
+ * `</object>`
+ * ```
+ *
+ * # Changing the Font
+ *
+ * Gtk CSS provides the best way to change the font for a `GtkSourceView` in a
+ * manner that allows for components like [class@Map] to scale the desired
+ * font.
+ *
+ * ```c
+ * GtkCssProvider *provider = gtk_css_provider_new ();
+ * gtk_css_provider_load_from_string (provider,
+ * "textview { font-family: Monospace; font-size: 8pt; }");
+ * gtk_style_context_add_provider (gtk_widget_get_style_context (view),
+ * GTK_STYLE_PROVIDER (provider),
+ * GTK_STYLE_PROVIDER_PRIORITY_APPLICATION);
+ * g_object_unref (provider);
+ * ```
+ * ```python
+ * provider = Gtk.CssProvider()
+ * provider.load_from_string("textview { font-family: Monospace; font-size: 8pt; }")
+ * style_context = view.get_style_context()
+ * style_context.add_provider(provider, Gtk.STYLE_PROVIDER_PRIORITY_APPLICATION)
+ * ```
+ *
+ * If you need to adjust the font or size of font within a portion of the
+ * document only, you should use a [class@Gtk.TextTag] with the [property@Gtk.TextTag:family] or
+ * [property@Gtk.TextTag:scale] set so that the font size may be scaled relative to
+ * the default font set in CSS.
+ */
+export const GtkSourceView = "GtkSourceView";
+export const VteTerminal = {
+    Root: "VteTerminal.Root",
+    ContextMenu: "VteTerminal.ContextMenu",
+};
+/**
+ * The central class of the WPE WebKit and WebKitGTK APIs.
+ *
+ * #WebKitWebView is the central class of the WPE WebKit and WebKitGTK
+ * APIs. It is responsible for managing the drawing of the content and
+ * forwarding of events. You can load any URI into the #WebKitWebView or
+ * a data string. With #WebKitSettings you can control various aspects
+ * of the rendering and loading of the content.
+ *
+ * Note that in WebKitGTK, #WebKitWebView is scrollable by itself, so
+ * you don't need to embed it in a #GtkScrolledWindow.
+ */
+export const WebKitWebView = "WebKitWebView";
+export const WebKitWebViewBase = "WebKitWebViewBase";
 /**
  * Sets the application-wide menu bar.
  * The menu will appear in the window's title bar on supported platforms.