qmlrs - QtQuick bindings for Rust
qmlrs allows the use of Qml/QtQuick code from Rust, specifically
- Rust code can create a QtQuick engine (QQmlApplicationEngine) with a loaded Qml script
- Qml code can invoke Rust functions
..with certain limitations. The library should be safe (as in not unsafe
) to use, but no promises
at this time. Reviews of the code would be welcome.
The library consists of a Rust part and a C++ part. The C++ part will be compiled automatically
when building with Cargo. You will need cmake
, Qt5 and a C++ compiler that can compile Qt5 code.
Your Qt5 installation should have at least the following modules: Core, Gui, Qml, Quick and Quick Controls.
If you are installing Qt5 from source, please note that passing "-noaccessibility" to the configure script disables the qtquickcontrols module.
If you want to use qmlrs add the following lines to your Cargo.toml:
[dependencies.qmlrs]
git = "git://github.com/cyndis/qmlrs.git"
This is the Rust code for an application allowing the calculation of factorials.
(Also contains a test for signals.)
You can find the corresponding Qml code in the examples
directory.
#![feature(core)]
#[macro_use]
extern crate qmlrs;
struct Factorial;
impl Factorial {
fn calculate(&self, x: i64) -> i64 {
std::iter::range_inclusive(1, x).fold(1, |t,c| t * c)
}
}
Q_OBJECT! { Factorial:
slot fn calculate(i64);
}
fn main() {
let mut engine = qmlrs::Engine::new();
engine.set_property("factorial", Factorial);
engine.load_local_file("examples/factorial_ui.qml");
engine.exec();
}
To run the above example, execute cargo run --example factorial
in the project's root directory.
Creating an Engine
automatically initializes the Qt main event loop if one doesn't already exist.
At least on some operating systems, the event loop must run on the main thread. Qt will tell you
if you mess up. The .exec()
method on views starts the event loop. This will block the thread
until the window is closed.
The code in this library is dual-licensed under the MIT license and the Apache License (version 2.0). See LICENSE-APACHE and LICENSE-MIT for details.