CXX-Qt: safe Rust bindings for Qt

• QMetaObject crate for Rust

  20 599 6.5 Rust

  Integrate Qml and Rust by building the QMetaObject at compile time.

  

There are a bunch of bindings with different language, but even the ones that are officially supported like PySide will still be second class citizen and awkward to use.

Automated binding generation will never give you idiomatic API in whatever language. And if you want an idiomatic library that wraps Qt, it's going to take a huge amount of work.

Which is why I think restricting to QML makes sense because that's a much smaller API surface. That was the ambition behind my previous crate that exposes QML to rust: https://github.com/woboq/qmetaobject-rs/

But now I've moved on to another GUI project: Slint https://github.com/slint-ui/slint

• cxx-qt

  28 901 9.6 Rust

  Safe interop between Rust and Qt

  

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• accesskit

  24 919 8.8 Rust

  UI accessibility infrastructure across platforms and programming languages

  

> from personal experience working on GUIs and toolkits for decades i think are overblown)

Accessibility and internationalization are really hard though, right?

I'm finally doing something about the accessibility issue: https://github.com/AccessKit/accesskit Still have a long way to go though.

• qtpy

  5 928 8.2 Python

  Provides an uniform layer to support PyQt5, PySide2, PyQt6, PySide6 with a single codebase

  

• ritual

  6 1,196 0.0 Rust

  Use C++ libraries from Rust

  

It is great to see how many people want to bring Qt support to Rust and are trying to do so, and I hope that these folks succeed, but it’s wearisome to me how they each create a new project instead of working with others who are already in this problem space. Of the half-dozen or so[0] existing attempts so far to create Qt bindings to Rust, none of them have actually succeeded because they’ve either been abandoned midway or limit their support to QML. Ritual[1] is the only crate I’ve seen that attempts to actually expose the whole Qt API, but it’s pretty awful to use, incomplete, and dead.

Rust doesn’t need more Qt crates. It needs one Qt crate that is complete and works well. (Or, ideally, a native Rust cross-platform GUI crate that works as well as Qt, but that’s an even longer and harder task.)

[0] https://lib.rs/search?q=qt

[1] https://github.com/rust-qt/ritual

• slint

  138 15,020 9.9 Rust

  Slint is a declarative GUI toolkit to build native user interfaces for Rust, C++, or JavaScript apps.

  

There are a bunch of bindings with different language, but even the ones that are officially supported like PySide will still be second class citizen and awkward to use.

Automated binding generation will never give you idiomatic API in whatever language. And if you want an idiomatic library that wraps Qt, it's going to take a huge amount of work.

Which is why I think restricting to QML makes sense because that's a much smaller API surface. That was the ambition behind my previous crate that exposes QML to rust: https://github.com/woboq/qmetaobject-rs/

But now I've moved on to another GUI project: Slint https://github.com/slint-ui/slint

• gyroflow

  74 6,078 9.6 Rust

  Video stabilization using gyroscope data

  

I think you can go quite far with Qt/QML and the qmetaobject crate. For example https://github.com/gyroflow/gyroflow

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

Suggest a related project