Current status of kdebindings

[Melton, Ryan]

Thanks for the work you are doing update Smoke to work with Qt5.   I maintain the Ruby qtbindings gem and would love  to get it updated to support Qt5.   My gem doesn't support KDE, but someone could backport the work I do into the KDE version.

Thanks,
Ryan

-----Original Message-----
From: Kde-bindings <kde-bindings-bounces at kde.org> On Behalf Of Chris Burel
Sent: Sunday, November 18, 2018 5:38 PM
To: kde-bindings at kde.org
Subject: Current status of kdebindings

Hi everyone!
It's been a while since I was really active on perlqt, but with the flurry of old bugs getting closed, I've been looking at it again. I haven't seen updates to any of the bindings in a long time, so I thought it would be a good time to check in with everyone and see what the state of everything is.

I've been working on a new version of smokegen that uses llvm to parse the headers, and have successfully built the smokeqt libraries against qt5, on Linux and MSVC. I'm trying to get it working now with mingw so that I can build PerlQt5 for Strawberry Perl. I also expect to get it to work on macos soon. Once I get the major platforms working, I'm planning on pushing the changes to the kde git repo and merging to master (I have them up on GitHub now while I've been developing, so I can do force pushes).

I know a lot of the other bindings depend on smoke, so this should unblock a bunch of stuff. But I don't know if any of the other bindings developers are still interested in supporting the old code, or updating it to work with qt5. On the kde techbase, I see Python, Perl, Ruby, C#, Java, and JavaScript listed. I know Python doesn't use smoke, but there still aren't (to my knowledge) pykde5 bindings available. All the others use smoke I believe. I only know Richard Dale used to support the Ruby bindings, but I haven't heard from him in a long while. Who supported the others?

-Chris

This message and any enclosures are intended only for the addressee.  Please 
notify the sender by email if you are not the intended recipient.  If you are 
not the intended recipient, you may not use, copy, disclose, or distribute this 
message or its contents or enclosures to any other person and any such actions 
may be unlawful.  Ball reserves the right to monitor and review all messages 
and enclosures sent to or from this email address.