Btw, if anyone in this latest thread doesn't know yet, you can substitute 3.20 into the URLs for documentation pointing at 3.22/3.24/stable and usually set something that's *almost* relevant, although 3.20 is increasingly old.
Failing that, hopefully your package manage installed the documentation into /usr/share/doc alongside the main package, or has a separate doc package available. On Thu, 14 Feb 2019 at 04:23, Compro Prasad via gtkmm-list < gtkmm-list@gnome.org> wrote: > 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.
_______________________________________________ gtkmm-list mailing list gtkmm-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtkmm-list
