3 ms·
Same here on all points. I am familiar w/ existing options to create Qt bindings in Rust, yet like other non-Qt-backed bindings (i.e. not PySide), they fall int
by kodablah 6y ago
Same here on all points. I am familiar w/ existing options to create Qt bindings in Rust, yet like other non-Qt-backed bindings (i.e. not PySide), they fall into disrepair or suffer on often needed features such as inheritance and slots.
I am kinda hoping autocxx[0] reaches the level of being able to handle wxWidgets headers (I have no hope for Qt though there are multiple Rust projects that try) and that will probably be enough for me on the desktop. Alternatively, it'd be nice to see a project that manually built Qt widget bindings surfacing an idiomatic Rust interface (kinda like what NodeGui does), but it's a lot of manual work that will have limited coverage in early stages instead of just continually improving/tweaking a generator.
0 - https://github.com/google/autocxx https://github.com/google/autocxx
- adamnemecek 6y agoI hope that wxWidgets for Rust never sees the light of the day.
- zozbot234 6y agoDoesn't wxWidgets have C-based bindings anyway, that Rust could use? How do they handle non-C++-based languages with existing support?
- kodablah 6y agoI am only familiar w/ wxc which wxHaskell used[0], but I do not know if they are still maintained. Granted after your sibling commenter mentioned concerns w/ wxWidgets, I may have research to do on concerns with using it in 2020 (e.g. reading the references of https://en.wikipedia.org/wiki/WxWidgets#Criticism https://en.wikipedia.org/wiki/WxWidgets#Criticism). 0 - https://github.com/wxHaskell/wxHaskell/tree/master/wxc https://github.com/wxHaskell/wxHaskell/tree/master/wxc