Hi, fellow haxers, and a Happy New Haxing year to you all!
Just found this very interesting multi-target Qt bindings library for Haxe:
Seems to be a very ambitious project with an interop solution that serves the frontend application from a go-lang backend (can not say that I undestand very much of that really works). Along with bindings for Haxe, there are Dart, Flutter and Swift bindings aswell, and more seem to be planned.
The Haxe codebase seems to be autogenerated and covers most basic GUI stuff. It uses Haxe 4.2 module level functions, so it’s obviously created by a guy that has some closer insight in Haxe.
make.sh project file includes a comprehensive Haxe target report, displaying what works and what doesn’t on the ALL different Haxe targets. Interestingly, --interp, jvm, java and cs status is currently “works” or “works-with-warn” while the the others have compile- or runtime errors.
When trying it out (on windows), I get --interp and jvm targets to compile, but they both give runtime error that seems to be caused in the interop message communication bus running at http://127.0.0.1:8000/.
The error message is the following:
No connection could be made because the target machine actively refused it. … so I guess it’s related to windows somehow not letting this interop communication through.
netsh http add iplisten 127.0.0.1:8000 but id doesn’t seem to help.)
Any ideas how to solve this?
Having a multi-target gui solution for Haxe is somewhat of a dream from my perspective, and the mother project https://github.com/therecipe/qt seems to be well maintained spread (8.1k stars, 615 forks). I don’t really have the knowledge to say something about the implications (pros/cons) with this interop approach, but maybe it can be a springboard to Qt development (with quick and easy compilation on --interp for example), later to be converted to fully native Qt applications…?
What do you think?