About 10 years ago I started a new hobby: Making
contributions to gtkmm and other mm modules. Along the way other
contributors have decreased their share in the development of
these modules. I have found myself adding the majority of new
patches. That was never my intention, but I wanted to have a
useful version of gtkmm4 when gtk4 became stable. That has
happened now. There are stable versions of gtk4, gtkmm4 and all
modules that gtkmm4 depends on.
In the future I intend to spend less time on mm modules than
I've done the last few years. An opportunity for other C++
programmers to enter.
Don't misunderstand me. I have not been alone. Other persons
have contributed. But I've done a greater part of the job than I
intended. And still gtkmm4 and the corresponding version of
gtkmm-documentation are not quite finished. Classes in gtk's gsk
subdirectory have not been wrapped in C++ code. Neither have
classes and methods that use structures from the graphene
library. Should there be a C++ binding of graphene? graphenemm?
Hopefully most users of gtkmm4 will not need the missing classes
and methods urgently. It's always possible to use the C
functions directly, although that's not what a C++ programmer
would love to do.