QMetaObject crate for Rust
Cursive
Our great sponsors
QMetaObject crate for Rust | Cursive | |
---|---|---|
20 | 22 | |
599 | 4,097 | |
2.3% | - | |
6.5 | 7.5 | |
about 2 months ago | 8 days ago | |
Rust | Rust | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
QMetaObject crate for Rust
-
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
-
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
Cursive
-
Projectable: A TUI file manager built for projects
Rust has great libraries for TUIs. tui-rs (https://github.com/fdehau/tui-rs) has been used in numerous popular applications, but is unmaintained. ratatui (https://github.com/tui-rs-revival/ratatui) is the maintained version, and is pretty new. Less widely known is cursive (https://github.com/gyscos/cursive), which I have yet to try.
Aside from the libraries, I just wanted to start a project that would make be better at Rust. The easy distribution with cargo is a huge bonus though.
- cursive: A Text User Interface library for the Rust programming language
-
How difficult is ncurses?
There are plenty of terminal UI libraries that are actually nice to work with. For Python, there's Textual and PyTermGUI. For Rust, there's ratatui and Cursive (or, if you want something a bit lower level, crosster or termion). For Go, there's bubbletea.
-
AMDGPU_TOP v0.1.2 - switch to crossterm-backend, add simple fdinfo viewer
Switching the backend of Cursive to crossterm removed dependence on ncurses
-
Appreciation post
I'd hear of TUIs so I just searched for tui libraries in Rust and Cursive seemed like a good choice and it turned out great!
-
Sharing Saturday #455
This weekend I started porting my game to a different UI library (egui) as a way of familiarizing myself with egui. I don't think I'll have something useable to build off of before this year's 7DRL challenge so I guess I'll be reusing my existing UI code (using cursive). But, once I finish porting the UI it should be a lot easier to add fancy stuff like animations, tooltips, and graphical tiles since I won't be tied to constraints of a terminal UI.
-
CLIs and TUIs packages
Cursive should let you easily build a layout with a menu and status bars (and mouse works).
-
Dwarf Fortress – randomly generated, persistent fantasy world
The thing that gets me about Dwarf Fortress is that it's a 64-bit text-mode game.
As a grey-haired developer who got excited about "DOS Extenders" that allowed 32-bit mode, seeing a text-mode game written as a native 64-bit application is bizarrely anachronistic.
I get a similar feeling from text-mode GUI frameworks for Rust, which allow multi-threading and 64-bit but are essentially clones of Borland Turbo Vision, where you had to be mindful to keep lists smaller than 64KB: https://github.com/gyscos/cursive
-
How to maintain app state in an app using Cursive
Maybe this helps?
-
Rust TUI libraries
cursive
What are some alternatives?
Slint - 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]
tui-rs - Build terminal user interfaces and dashboards using Rust
slint - Slint is a declarative GUI toolkit to build native user interfaces for Rust, C++, or JavaScript apps.
Termion - Mirror of https://gitlab.redox-os.org/redox-os/termion
wxRust - A Rust binding of the wxWidgets cross platform toolkit.
ncurses-rs - A low-level ncurses wrapper for Rust
Rust Qt Binding Generator git - Generate bindings to use Rust code in Qt and QML
rustbox - Rust implementation of the termbox library
Native Windows GUI - A light windows GUI toolkit for rust
rust-sciter - Rust bindings for Sciter
ritual - Use C++ libraries from Rust
conrod - An easy-to-use, 2D GUI library written entirely in Rust.