diff options
author | Emmanuele Bassi <ebassi@gnome.org> | 2022-10-24 20:04:03 +0100 |
---|---|---|
committer | Emmanuele Bassi <ebassi@gnome.org> | 2022-10-24 20:11:50 +0100 |
commit | 21bc2c507891bd41444d52736b0df08b16c94cba (patch) | |
tree | 4ea9796430a63e0c3718070aaa438414ec42af90 /gtk/gtkwidget.c | |
parent | a95cfb1c457cbd3ff365f7f1244c42dda8540b66 (diff) | |
download | gtk+-21bc2c507891bd41444d52736b0df08b16c94cba.tar.gz |
docs: Remove mentions of Glade
Glade does not support GTK4, so we should not link to it when discussing
developing GTK4 applications.
Diffstat (limited to 'gtk/gtkwidget.c')
-rw-r--r-- | gtk/gtkwidget.c | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/gtk/gtkwidget.c b/gtk/gtkwidget.c index b57d8c340c..47aa0b5c5c 100644 --- a/gtk/gtkwidget.c +++ b/gtk/gtkwidget.c @@ -321,14 +321,14 @@ * The interface description semantics expected in composite template descriptions * 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 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 required for UI design tools like - * [Glade](https://glade.gnome.org/) to introspect what kind of properties and - * internal children exist for a given type when the actual type does not exist. + * 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 + * 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 |