forked from AuroraMiddleware/gtk
873f6ccfea
This shows how to use a layout manager in a widget, implemented in javascript. The example sets up the environment for running from the toplevel dir, assuming that the build dir is called 'build'. |
||
|---|---|---|
| .. | ||
| application1 | ||
| application2 | ||
| application3 | ||
| application4 | ||
| application5 | ||
| application6 | ||
| application7 | ||
| application8 | ||
| application9 | ||
| bp | ||
| hello | ||
| action-namespace.c | ||
| builder.c | ||
| builder.ui | ||
| drawing.c | ||
| grid-packing.c | ||
| labels.js | ||
| meson.build | ||
| plugman.c | ||
| README | ||
| search-bar.c | ||
| squares.py | ||
| sunny.c | ||
| window-default.c | ||
= Examples =
== Building the examples ==
The examples in this directory are built alongside the rest of GTK.
The examples under the `application[1-9]` directories are also included in
the GTK API reference documentation, and can be built independently, using
the system libraries, by doing:
$ cd application1
$ make -f Makefile.example
== Running the examples ==
The examples can be run uninstalled.
The later demos are using GSettings,so they need a GSettings schema.
The code for these demos contains a workaround to look for the schema
in the current directory, so this works:
$ cd application5
& ./exampleapp window.ui