News for hackers. Stuff that matters.
Re:Cross-Platform GUI Toolkit Trainwreck (2016) by grawprog on Thursday April 25, 2019 @10:23AM (#19748431)
Huh?

https://wiki.qt.io/Language_Bindings

5.1 Qt for Python (PyQt)

5.2 Qt for Ring (RingQt)

5.3 Qt for Rust (Rust-Qt)

5.4 Qt Quick for Rust (qml-rust)

5.5 Qt Quick for Rust (qmlrs)

5.6 Qt for Crystal (qt5.cr)

5.7 Qt for Go (qt)

5.8 Qt for C#/Mono/.Net (QtSharp)

5.9 Qt for C#/Mono/.Net (Qml.Net)

5.10 Qt for D (QtE5)

5.11 Qt for Haskell (qtHaskell)

5.12 Qtah

5.13 Qt for Julia (QML.jl)

5.14 Qt Quick for Haskell (HsQML)

5.15 Qt Quick for OCaml (lablqml)

5.16 Qt Quick for Node.js (Brig)

5.17 QML bindings for Nelson language

Re:Cross-Platform GUI Toolkit Trainwreck (2016) by rapsey on Thursday April 25, 2019 @10:52AM (#19748764)
Most of these are limited to the point of uselesness.
Re:Cross-Platform GUI Toolkit Trainwreck (2016) by doubleunplussed on Thursday April 25, 2019 @11:44AM (#19749316)
I ship nontrivial PyQt apps. PyQt can basically do anything Qt can do. Multiple inheritance of QWidgets can be dicey, but desired results can usually be achieved by defining mixins that don't subclass QWidget. It works brilliantly, far from "the point of uselessness". For me, cross platform GUIs are a solved problem, and I really can't wrap my head around all the noise to the contrary, or the claims that electron is what saved us.
Re:Cross-Platform GUI Toolkit Trainwreck (2016) by rapsey on Thursday April 25, 2019 @11:51AM (#19749386)
Yeah that is why I said C++ and python...
Re:Cross-Platform GUI Toolkit Trainwreck (2016) by doubleunplussed on Thursday April 25, 2019 @11:57AM (#19749450)
Apologies, didn't see that
Re:Cross-Platform GUI Toolkit Trainwreck (2016) by billfruit on Thursday April 25, 2019 @01:21PM (#19750346)
Python QT bindings are poorly documented, much of the documentation is out of date. Also it appears to me, far too much churn.
Re:Cross-Platform GUI Toolkit Trainwreck (2016) by doubleunplussed on Tuesday April 30, 2019 @07:31PM (#19793064)
I don't use PyQt's documentation (wasn't even aware it really existed), it's such a literal wrapper that you can just use Qt's documentation.

And the only churn was a change about five years ago from a less pythonic API (using wrapped Qt types for most things) to a more pythonic one (using Python's native types where it makes sense). And that wasn't even that bad. Other than that it has no more churn than Qt itself does.

Re:Cross-Platform GUI Toolkit Trainwreck (2016) by pknopf on Friday April 26, 2019 @12:41PM (#19759366)
I am the author of Qml.Net.

With it, you have the full power of .NET Core and QML. There really isn't any limits.

https://github.com/qmlnet/qmlnet

Re:Cross-Platform GUI Toolkit Trainwreck (2016) by grawprog on Thursday April 25, 2019 @12:25PM (#19749721)
I use the D bindings to qt regularly when I'm not using dlangui for GUI.
Re:Cross-Platform GUI Toolkit Trainwreck (2016) by aerique on Thursday April 25, 2019 @04:02PM (#19751974)
The Common Lisp bindings (EQL) are solid as well.
Re:Cross-Platform GUI Toolkit Trainwreck (2016) by krageon on Thursday April 25, 2019 @11:38AM (#19749247)
Quoting an article's (no doubt extensive) list of bindings for whatever library isn't a great way to start off a conversation about usable bindings in a given language. Bindings often exist, but they are not often any good.