orbtk
vgtk
Our great sponsors
orbtk | vgtk | |
---|---|---|
10 | 14 | |
3,772 | 1,038 | |
0.0% | - | |
0.0 | 0.0 | |
over 1 year ago | about 2 years ago | |
Rust | Rust | |
MIT License | GNU General Public License v3.0 or later |
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.
orbtk
-
Masonry 0.1 (Rust GUI framework)
i was gonna bring up https://github.com/redox-os/orbtk only to discover it's no longer under active development.
-
[Media] A GUI installer for redox is coming soon, written in iced!
OrbTk is sunsetting in favor of Iced, slint, and future renderer-agnostic toolkits: https://github.com/redox-os/orbtk
-
Pure Rust GUI Landscape
Orbtk
-
S76 firmware repo password?
The GitLab repo was deleted. You will need to update the submodule path to https://github.com/redox-os/orbtk.
-
GTK and custom themes - what really happened
That said, I'm not totally convinced about SixtyFPS today. There are some other interesting options that are suitable GUI toolkits for Rust. Such as OrbTk and Iced. Each toolkit is approaching the GUI space in a different way, so it'll be interesting to see where we end up in a few more years. QML-esque SixtyFPS, ECS-based OrbTk, Elm-based Iced, and a few others out there.
-
Pop should join this new GTK fork
What's written in this article isn't the development of a GTK fork, but some reasoning for exploring alternatives to GTK. There aren't very many suitable candidates in this space, but Rust GUI toolkits like Iced have potential. Personally, I would add that OrbTk is also a suitable candidate.
-
Any stable crate to develop a cross-platform Rust desktop app?
I use orbtk, it is pretty easy to use, has an active dev team, works on windows mac and linux, and cross compiling from linux to windows is also easy with it. It is still pretty beta, but depending on the project you need it could work. (https://github.com/redox-os/orbtk)
-
Cross platform native guis in rust
Orbtk is an option. The default is backend is orbraq, which uses OrbClient. OrbClient will use SDL on Linux, and on Redox it should be a "pure" rust experience.
-
Rust GUI: Introduction, a.k.a. the state of Rust GUI libraries (As of January 2021)
OrbTK recompiling stuff has been fixed in the development branch as far as I can tell: https://github.com/redox-os/orbtk/pull/409
OrbTK
vgtk
-
Rust: State of GUI, December 2022 – KAS blog
A pretty fun Rust GUI experienc is vgtk[0], which is doing a bunch of macro magic to give a "we're coding in React" vibe to GTK+. I don't really have a specific thing I want to code in a native GUI at the moment but if I did I think this would be the most tempting for me.
[0]: https://github.com/bodil/vgtk/
-
Code bloat has become astronomical
a stateful GUI markup language is react. it is not yet the case that react-like code works for desktop, though there are cool examples like vgtk https://github.com/bodil/vgtk
- Vgtk - A declarative desktop ui framework for rust built on gtk and gtk-rs
-
A declarative desktop UI framework for Rust built on GTK and GTK-rs
from what i gather from https://github.com/bodil/vgtk/issues/78, you're better off using realm
I'm always curious to see these projects, because I've been experimenting with a React renderer for the GJS bindings for a while. It's frustrating because GTK "feels like" it's so close to being able to support a vdom/declarative paradigm, but the devil is in the details.
The simple use-cases like "Window > Box > Label" are easy to get going. The more complex widgets like Stack/Grid/TreeView ... aren't.
This project seems to have the same issue: https://github.com/bodil/vgtk/issues/40
This is made more difficult now GTK4 has removed the Container base class, so there's no longer a unified interface for adding children (although it had caveats in the first place).
I totally get the GTK view that (presumably) specific widgets are more intuitive with specific add/remove APIs (like the grid - one doesn't really "appendChild" to a grid).
It just feels like: if there was a consistent container API comparable to the web's appendChild approach, a vdom/declarative approach would require only a very light wrapper. Without it, I keep coming back to the idea of implementing wrapper widgets that expose that consistent API instead. And that's just not something I want to maintain - effectively duplicating each GTK widget for the purpose of making it fit into a tree model.
It's also a problem of trying to wrap richer functionality (pack_start and pack_end) into a simpler set (append only) of course.
So I don't know exactly what my point is :) Perhaps cautioning the reader that the simplicity of the approach comes with a catch.
-
Hacker News top posts: May 28, 2022
A declarative desktop UI framework for Rust built on GTK and GTK-rs\ (23 comments)
-
Newbie here. Just finished reading the book. What now?
Build your own To-do List Application in Rust: https://bodil.lol/vgtk/
What are some alternatives?
Azul - Desktop GUI Framework
neon - Neon: Serverless Postgres. We separated storage and compute to offer autoscaling, branching, and bottomless storage.
iced - A cross-platform GUI library for Rust, inspired by Elm
headway - Self-hostable maps stack, powered by OpenStreetMap.
egui - egui: an easy-to-use immediate mode GUI in Rust that runs on both web and native
areweguiyet - A website built for the Rust community
Native Windows GUI - A light windows GUI toolkit for rust
piet - An abstraction for 2D graphics.
druid - A data-first Rust-native UI design toolkit.
Relm4 - Build truly native applications with ease!
conrod - An easy-to-use, 2D GUI library written entirely in Rust.
libui - Simple and portable (but not inflexible) GUI library in C that uses the native GUI technologies of each platform it supports.