Perhaps it'd be nice if there were a 'Documentation' button beneath the code examples that takes you to the appropriate page in the Docs.

There doesn't need to be any further instructions on the landing page, though. Again, that's what the docs are for.

This is terrible. Even the example on the documentation page doesn't work. One has to go to the issues page on github for gtk-rs to find that the documentation in its current form is incorrect.

So, neither the example on the page nor the documentation work.

How desperate should one be to want to use GTK? Is this some kind of an initiation?

PS. I can't reply to this thread any further.

I'll concede that I may be making a mistake copying and pasting things, but I've checked a few times. If the job of the documentation is to help, then it should address situations where people get stuck.

At this stage, the new gtk webpage feels akin to putting lipstick on a pig.

PPS. Seems like I can reply again.

We're just taking your word for this. For all I know, you're making some mistake or skipping some step and blaming it on the documentation.

I'm not sure if you're implicitly wanting us to diagnose your issue for you without providing any actual information, but seeing as I have no idea if you have GTK properly installed, the headers in the right place, or anything else like that, I can't help but be sceptical that the documentation isn't up to snuff.

Oh, I didn't realize I had to install GTK separately - that I couldn't just include the libraries in my Cargo.toml and hope the compilation would do it.

So, I went to part of the GTK Project page where it provides examples on how to install GTK for Mac (https://www.gtk.org/docs/installations/macos/) and clicked on the installation script link under Getting Started. The installation script link is broken.

You would normally use Homebrew or MacPorts anyway.