A type-safe, builder-pattern-driven Qt6 GUI library for Rust. Built on cxx for zero-cost C++ interop, with RAII memory management and signal/callback bridging.

• Builder pattern — chain .title("X").size(800, 600).build()
• RAII cleanup — automatic C++ deletion, parent-child aware (no double-free)
• Signal bridging — Qt signals invoke Rust closures via a global trampoline
• Layout ownership — adding a widget to a layout transfers ownership
• .ui file loading — load Qt Designer .ui files at runtime
• Zero unsafe in public API — all FFI is encapsulated

use qtrs::prelude::*;

fn main() {
    let app = Application::new();

    let mut window = Widget::new()
        .title("Hello, qtrs!")
        .size(400, 300)
        .build();

    let mut layout = VBoxLayout::with_parent(&window);

    let btn = PushButton::new("Click me")
        .on_clicked(|| println!("clicked!"))
        .build();
    let label = Label::new("Welcome!").build();

    layout.add(btn);
    layout.add(label);

    window.set_layout(&layout);
    window.show();

    app.exec();
}

You can see demo.rs for details.

Qt6 with development headers:

Remember to set a PATH environment to tell qtrs where the qmake are.

Add to your Cargo.toml:

[dependencies]
qtrs = "0.5.7"

Widgets are deleted automatically on Drop — unless they have a Qt parent (set explicitly or via layout). In that case Qt's parent-child tree handles deletion, preventing double-free.

Widget created without parent  ->  Drop deletes C++ object
Widget created with parent     ->  Drop skips deletion (Qt handles it)
Widget added to layout         ->  Layout takes ownership, Drop skips deletion

Qt GUI classes are not thread-safe. All widget creation, mutation, and the event loop must happen on the main thread.

MIT OR Apache-2.0 — see LICENSE-MIT and LICENSE-APACHE.