summaryrefslogtreecommitdiff
path: root/gtk/gtkbuilderscope.h
Commit message (Collapse)AuthorAgeFilesLines
* Use the appropriate prefix for GtkBuilderClosureFlagsEmmanuele Bassi2020-12-011-1/+1
| | | | | Facilitate the job of glib-mkenums, and ensure that the enumeration nicknames are computed reliably.
* gtk/enums: fix doc comment referencesDavid Lechner2020-11-071-1/+1
| | | | Enum members need a "%" prefix rather than "@" or "%@" in order to automatically create links in the documentation.
* docs: Clean up many dangling linksMatthias Clasen2020-08-041-1/+1
| | | | | In many cases, these were references to no longer existing api, so some rewording was necessary.
* Replace "gchar" with "char"Benjamin Otte2020-07-251-3/+3
|
* builder: Turn last dlsym() function into a scope APIBenjamin Otte2019-12-121-0/+8
| | | | | Looking up a get_type function by its name is now also part of GtkBuilderScope.
* builder: Add GtkBuilderScopeBenjamin Otte2019-12-121-0/+116
GtkBuilderScope is an interface that provides the scope that a builder instance operates in. It creates closures and resolves types. Language bindings are meant to use this interface to customize the behavior of builder files, in particular when instantiating templates. A default implementation for C is provided via GtkBuilderCScope (to keep with the awkward naming that glib uses for closures). It is derivable on purpose so that languages or extensions that extend C can use it. The reftest code in fact does derive GtkBuilderCScope for its own scope implementation that implements looking up symbols in modules. gtk-widget-factory was updated to use the new GtkBuilderCScope to add its custom callback symbols. So it does it different from gtk-demo, which uses the normal way of exporting symbols for dlsym() and thereby makes the 2 demos test the 2 ways GtkBuilder uses for looking up symbols.