3 ms·
Like the more mature <https://invent.kde.org/sdk/rust-qt-binding-generator https://invent.kde.org/sdk/rust-qt-binding-generator> this project avoids binding exi
by oever 5y ago
Like the more mature <https://invent.kde.org/sdk/rust-qt-binding-generator https://invent.kde.org/sdk/rust-qt-binding-generator> this project avoids binding existing C++ code, but makes rust code available to C++/QML projects.
- sho_hn 5y agoBeing familiar with your project I'm curious how this new one differentiates itself (other than being built on cxx).
- oever 5y agoRQBG is not changing a lot any more because for me it works fine and some people are using it. There's currently one patch in the works, but other than that it's stable. Initially, I blogged quite a bit and put effort into good demo applications. But no feature requests or patches were forthcoming. Which is fine by me. The project was meant to be simple and stay simple. This project takes the same approach. It is aimed to put Rust at the core (business logic) of the application and code the UI in C++ or QML. This way you sidestep the enormous work of writing bindings for the Qt libraries. Here's a talk on the idea. <https://archive.fosdem.org/2018/schedule/event/rust_qt_binding_generator/ https://archive.fosdem.org/2018/schedule/event/rust_qt_bindi...> KDAB hires some of the best Qt coders, so this effort by them might get more traction. Using macros and annotations like Oliviers project is nice. When RQBG started procedural macros were not attractive yet. This new project is on Microsoft GitHub which means I won't be contributing. I prefer to work on projects that are self-hosted by communities like KDE, GNOME, Debian instead of being locked on a closed platform of a competitor.