GitLab

Require gtkmm and giomm only if build-examples=true
or a tarball is being built.

Remove a dead link. Update some jhbuild info. Mention gnome-build-meta.

and suggest filing GitLab issues and merge requests.

Should have been done when Meson build dropped the dependence on Perl.

Links in the patch added by Kjell Ahlstedt.
Fixes #4

* tools/tutorial/insert_example_code.py: New Python file, equivalent to
the insert_example_code.pl Perl file.

The Perl file is still used when building with Autotools.

and use 'with' in Python code when files are opened.

Fixes #12

The configuration with Autotools or Meson sets the compiler
option -DDONT_HAVE_MKFIFO=1, if mkfifo() does not exist.
Meson does not create build/config.h.
This makes life easier for those who build with their own
Makefile or CMake file or whatever.
Fixes #11

Appendix G. Wrapping C Libraries with gmmproc: Describe how the
skeletonmm project is built with Meson (was Autotools).

And add 'dist-warnings' with default value 'fatal'. It's used when a
tarball is tested by 'ninja dist' or 'meson dist'.

The bash command may not be available, e.g. in Windows.
Use python instead of bash in 'ninja examples'.

See https://mail.gnome.org/archives/gtkmm-list/2019-December/msg00014.html
Fixes #9 (Danny van Elsen)

* docs/tutorial/C/index-in.docbook: Change URLs.
* docs/tutorial/insert_example_code.pl: Don't add url_examples_branchsuffix.
The branch is not a suffix in gitlab, it's included in url_examples_base.

!7 (comment 655543)

constness isn't the issue here; rather it is the value class of the
argument of set_group(). That method needs an lvalue reference as it
modifies the Group by adding the RadioButton to it. That's why we can't
`rb2.set_group( rb1.get_group() )`. But we can store the Group returned
by get_group() in a variable and then pass that to set_group() calls.
Not that there is much reason to, given join_group(), but it works fine.

Then I got carried away and added a program listing showing it
working... which, while mostly superfluous, does provide a nice
opportunity to explain briefly that RadioButtonGroup is a handle type,
meaning that it can be declared automatically and discarded by RAII
without worrying about thusly releasing the RadioButtons from itself.
That then informs readers for the next example that creates a new Group.

This is the first use of either "lvalue" or "rvalue" in the docbook!
That's either a good thing or a slippery, slippery slope to start on...

!6

The 2nd example seems to have been trying to be like the 1st, which put
the 3 RadioButtons in a subclass of Window, for no real reason since
they were never then added to said Window... but the 2nd omitted to
declare its members and instead declared new local variables in the
constructor with m_ prefixes, which were managed unlike the 1st example!

Just drop all of that. There's no clear reason to use a containing class
here. By not doing so, we can present both examples in a comparable way.

!6

Instead, recommend an std::unique_ptr, which will destroy it via RAII,
rather than requiring that the user remember to `delete` it and have to
define a non-trivial destructor just to do that, which is just busywork.

!7

…2.62, which as of Kjell’s simply epic recent commits, now supports us
setting custom properties of gtkmm-derived widgets in .ui files for
Builder. Also, slightly elaborate the bit about why you would want to!

I also be optimistic here and presume that such properties could be made
editable in Glade by using a custom catalog and property classes,
though my Glade-fu is weak, so I can only hope I'm inferring that right.

!5

Print a message to stderr when a file can't be opened.

step1/exampleapp.desktop was renamed to exampleapp.desktop.in in the
previous commit, but the filename was not changed everywhere.

Python scripts can be used on all operating systems where Meson
can be used. Shell scripts are restricted to Unix-like systems.

Add a DerivedButton that contains Glib::Property members.

* examples/book/application/command_line_handling/exampleapplication.[cc|h]:
Add some options that demonstrate the use of
Gio::Application::add_option_group().

See issue glibmm#46

Use the / operator instead of join_paths().
Directory paths for installation are relative to {prefix} instead of absolute.
Don't call meson.add_dist_script(), if it's a subproject.
Use MESON_DIST_ROOT in extra-dist-cmd.sh.

Posix does not support long options for the cp, rm and mkdir commands.
See mm-common!1

bash isn't always installed in /bin. Scripts which don't require bash
to work are converted to use sh, while scripts requiring bash features
are changed to use PATH to find bash.

See the mm-common!1 MR.

* examples/book/buildapp/README:
* README: meson, not autotools, is now the recommended build system.

New files copied from git's master branch and modified where necessary.
See the README file for instructions how to use it.

* examples/book/buildapp/README: Describe how to build with meson and ninja.
* examples/book/buildapp/step1/install-cmd.sh:
* examples/book/buildapp/step[1-9]/meson.build: New files

Add MyExtraInit that calls gtk_widget_class_set_css_name() in the class init
function and calls gtk_widget_set_has_window() in the instance init function.
See glibmm#33