I am also frustrated with
the documentation available for gtkmm. I
have to instead look into gtk docs and try to guess the
equivalent
gtkmm code. If possible I could also help in doing anything
necessary
or automating the whole process document generation.
Documentation *is* largely generated, and usually people
complain about that instead because the generation (A) is
inherently limited because not every C concept can be 100%
accurately transformed to a C++ wrapping mechanistically
and/or (B) said automation doesn't have all the features
that it in theory could (but which I don't see Merge
Requests for! ...yes, including from myself.)
I presume you've seen the gtkmm tutorial (in the
gtkmm-documentation project). If there are specific things
you are frustrated with, then you can submit an Issue or -
better - Merge Request on GitLab to request or add examples
for that. Otherwise, it's unclear what you want fixed, or
where you think *more* automation could help (rather than
hinder), so general frustrations don't really provide an
indication of what could be improved.
