{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiapqaizrafj3hpda2u4wef2mzz37u5la3vypmewb3m3nsnwol56p4",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mlslci5udt32"
  },
  "path": "/viewtopic.php?t=33365&p=273994#p273994",
  "publishedAt": "2026-05-14T09:44:42.000Z",
  "site": "http://forum.palemoon.org",
  "tags": [
    "https://git.devuan.org/Daemonratte/gtk2-ng-themes",
    "https://git.devuan.org/Daemonratte/gtk2-ng-engines",
    "https://git.devuan.org/SteveM/DTK_debs",
    "https://git.devuan.org/greenjeans/gtk2-ng-test-scripts",
    "https://sourceforge.net/projects/vuu-do ... g-testing/"
  ],
  "textContent": "> ...\n\nSorry for the late reply. I'm not getting any email notifications and just noticed there are many new comments.\nWe still didn't tidy up or test all the engines and themes, but we started collecting them here:\nhttps://git.devuan.org/Daemonratte/gtk2-ng-themes\nhttps://git.devuan.org/Daemonratte/gtk2-ng-engines\n\nThere are binaries available now too:\nhttps://git.devuan.org/SteveM/DTK_debs\n\nAnd greenjeans wrote some scripts and isos that make it way easier to test it\nhttps://git.devuan.org/greenjeans/gtk2-ng-test-scripts\nhttps://sourceforge.net/projects/vuu-do ... g-testing/\n\nAbout the warnings: I fixed MANY more and not there are no introspection errors anymore. I wonder if the original gtk2 developers broke bindings for other languages and just never fixed it.\n\n\n> ...\n\nWhen I watched that video, I was really mad\n\n> \"You preserved something. Meaning you didn't change anything.\"\n> \"there's a bunch of random little [fixes] out there\"\n> \"a lot of the changes being done are either merging existing work that has been done\"\n\nFirst of all, when I started compiling gtk2 gave me 2mb of compiler warnings. Now I only get around 130 depending on how many threads I use. Fixing some warnings was easy. Others required me to rewrite code segments and then fix errors I got from the rewrites.\nI also noticed that aparently they just let this toolkit ROT. There were bugs in the demos, in the build script, in the code, etc and a couple days ago I merged over 100 commits that fixed introspection errors. They literally messed up GIR metadata (you need that for bindings for Python, JavaScript, C#, Perl, Ruby, etc) and I digged through the code to fix it. I could have chosen to simply mute all the compiler warnings, but I fixed them.\nSo yes! The fact that we didn't break anything is something we can be proud of.\nI also included fallbacks so you can compile it on anything from Debian 8 to bleeding edge distros like Arch and Gentoo.\n\nHim saying that all we did was merging existing patches also really pissed me off. Just look at how many commits I added. Hundreds. There aren't hundreds of patches out there that I could have applied.\n\nNot trying to be a kissass, but all of this let's me respect your work even more, because now I know exactly what you had to endure for years.\n\n\n> ...\n\nThat's also how I found out about him. In the beginning he really just copied Luke Smith.\n\n* * *",
  "title": "Other/future projects • Re: GTK2 revival",
  "updatedAt": "2026-05-14T09:44:42.000Z"
}