SaaSHub helps you find the best software and product alternatives Learn more →
QMetaObject crate for Rust Alternatives
Similar projects and alternatives to QMetaObject crate for Rust
-
-
CodeRabbit
CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
-
-
Bootstrap
The most popular HTML, CSS, and JavaScript framework for developing responsive, mobile first projects on the web.
-
-
-
-
slint
Slint is a declarative GUI toolkit to build native user interfaces for Rust, C++, or JavaScript apps.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
-
-
-
Slint
Discontinued Slint is a toolkit to efficiently develop fluid graphical user interfaces for any display: embedded devices and desktop applications. We support multiple programming languages, such as Rust, C++ or JavaScript. [Moved to: https://github.com/slint-ui/slint]
-
-
-
-
-
-
-
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
QMetaObject crate for Rust discussion
QMetaObject crate for Rust reviews and mentions
-
9 years of Apple text editor solo dev
You can use Rust with QML[1].
QML is actually pretty amazing. I've been building my block editor[2] view entirely in QML while the model is in C++. This separation of logic and presentation works great. And yes, there are some crashes sometimes (that I find quite easy to debug thanks to the built-in debugger), but take for example a similar app that's built with Rust and Dart[3], in my testing there were still memory leaks that caused my computer to hang. It's better to know you have a bug than for it to be hidden from you.
I agree with parent commenter, saying these cross-platform frameworks will end up supporting the least common denominator set of features. But I found with external open source libraries, the community is catching up very fast. For example, you want the awesome translucency macOS apps have for your Qt app? Here you go[4]. Many such cases. It's also pretty straightforward to add your own custom OS-dependent code, especially so, if someone already open sourced his approach. I recently wanted to move the traffic light buttons on macOS for my app, but couldn't figure the Objective-C code for that. I ended up looking at either Tauri or Electron source code and found my answer.
[1] https://github.com/woboq/qmetaobject-rs
[2] https://www.get-plume.com/
[3] https://www.appflowy.io/
[4] https://github.com/stdware/qwindowkit
-
I like rust but want to use Qt.
I just used qmetaobject-rs and my experience with Qt/QML. There's the QML book from Qt if you're just starting, which is pretty nice https://www.qt.io/product/qt6/qml-book
- GUI development with Rust and GTK 4
-
Made my first app in Rust! A notification daemon for Linux :)
qmetaobject is probably the most mature Qt Rust binding at the moment. It uses the cpp crate to embed C++ inline in Rust to create its bindings. There are some people using it and it does get some maintenance, but it's not under active development since the original author is now working on Slint.
- QT for Rust?
-
Using KConfig with Rust
The bindings currently use the git version of qttypes since I had to merge some upstream changes that are needed for these bindings. So they are not ready for prime time just yet.
-
CXX-Qt: safe Rust bindings for Qt
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
-
Why does Rust code compile into a single executable binary?
Whisperfish does this with Qt: https://github.com/woboq/qmetaobject-rs/issues/102
-
Announcing Gyroflow - an advanced video stabilization tool written in Rust with GPU acceleration and cross-platform UI
What do you want to know? It's pretty easy thanks to the amazing work of guys behind qmetaobject-rs.
-
Using KI18n with Rust and Qml
This is probably the portion that I found the most difficult. The README of qmetaobject-rs gives us a basic idea of the build script, so I started with that. Here is my starting script
-
A note from our sponsor - SaaSHub
www.saashub.com | 11 Feb 2025
Stats
woboq/qmetaobject-rs is an open source project licensed under MIT License which is an OSI approved license.
The primary programming language of QMetaObject crate for Rust is Rust.
Popular Comparisons
- QMetaObject crate for Rust VS wxRust
- QMetaObject crate for Rust VS Slint
- QMetaObject crate for Rust VS ritual
- QMetaObject crate for Rust VS Rust Qt Binding Generator git
- QMetaObject crate for Rust VS femtovg
- QMetaObject crate for Rust VS Native Windows GUI
- QMetaObject crate for Rust VS qt.rs
- QMetaObject crate for Rust VS slint
- QMetaObject crate for Rust VS Azul
- QMetaObject crate for Rust VS conrod