You can use Devhelp to read the documentation of functions etc.
I don't know any easy way to find the source code. Searching for the name in Gitlab won't be that efficient, since functions usually are defined once and used many times.
In your specific example, g_return_if_fail
is part of Glib not Gtk (as indicated by the g_
prefix) and it is a macro not a function. You can find its definitions by searching for define g_return_if_fail
in Glib.
I provide my Gtk3 application written in C99 to M$ windows. https://cygwin.com/ would be a good point to start with.
If you have to use mingw to compile source code, I would recommend to cross compile from GNU+Linux. I experienced that the job was done much faster.
Some feedback about the new documentation: - Big logo on sidebar leaves less space for actual links - The font pairing (RedHat/Noto, sans-serif/serif) is a bit weird, you might as well use RedHat (Text and Display) for everything if you're gonna include both. - Search results are bad, replacing the stemmer altogether with fuzzy searching would be way more useful (e.g. the fzy algorithm is great) - I'd be happy to help, but I've taken a look at the repo and your build system and it all seems quite dated from a javascript development perspective, I'd at least bundle all the files in a single one and avoid using globals in multiple files by using a import/export syntax. If you're interested let me know I can open a PR with the adjustments above.
> after a couple of days of work? Yeah, I just quit it.
You can't really learn a new UI framework from scratch and develop a complete app in just "couple of days".
> having separated logic & view languages and system dramatically reduces the productivity
Yeah... that's what MVC is.
Flutter is build around Dart, and the worst is : "Dart tools may send usage metrics and crash reports to Google" (source: https://dart.dev/get-dart#install). Even if analytics aren't enabled in the release version that's a big no-no for me.