case-studies
egui
case-studies | egui | |
---|---|---|
11 | 204 | |
1,603 | 19,841 | |
- | - | |
3.8 | 9.8 | |
about 1 month ago | 6 days ago | |
Rust | Rust | |
Apache License 2.0 | MIT OR Apache-2.0. |
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.
case-studies
-
::lending-iterator — Lending/streaming Iterators on Stable Rust (and a pinch of HKT)
Luckily there is a workaround to emulate such a definition, which dtolnay discovered and explained here: https://github.com/dtolnay/case-studies/tree/b9802f6df8dc8e54970b83fb9af6df923b46abf5/unit-type-parameters.
-
Hey Rustaceans! Got a question? Ask here! (17/2022)!
I think they are talking about this one trick which the devs don't want you to know about. Note that while it looks like specialization, it works only in a few very limited cases and is quite fragile, so it's a hack, not a substitute for the real feature.
-
Any good resources for learning Rust macros?
Also I suggest his case studies repo since you are looking at what is possible: https://github.com/dtolnay/case-studies
-
What are some creative/advanced uses of macro_rules?
/u/dtolnay has a great case studies repository.
-
Hey Rustaceans! Got an easy question? Ask here (29/2021)!
Once you have the basics down, read dtolnay's case studies. They show how to do advanced stuff with easy macros.
-
println use `Debug` if argument is not `Display`
If you were writing your own println macro, you might be able to get away with this kind of hack: https://github.com/dtolnay/case-studies/blob/master/autoref-specialization/README.md
-
Hey Rustaceans! Got an easy question? Ask here (11/2021)!
You can use "Autoref-based stable specialization" or use/mimic the impls crate.
-
Why I gave up on Rust (for now)
With a subset of specialization likely riding the trains soon and a workaround available, why would you give up?
-
Hey Rustaceans! Got an easy question? Ask here (10/2021)!
this works since values and types are in different namespaces (see: Rusts Universes or dtolnay's Case Study about "Unit struct with type parameters")
-
Hey Rustaceans! Got an easy question? Ask here (53/2020)!
To do this with traits you would need specialization but since you are using macros you should be able to use "Autoref-based stable specialization". Here is a playground which uses the latter approach to implement the wanted macro without using any nightly features.
egui
-
Macroquad egui DevTools: Rust Game Debugging UI
Probably the hardest part, if you are new to egui, is to work out how to display the widgets you want. The egui demo site is quite handy in this regard. It features the egui widgets, and has GitHub links to the Rust code used to make each widget. This will help you replicate them in your own project.
-
Egui 0.27 – easy-to-use immediate mode GUI for Rust
Thanks for the feedback!
It is definitely fixable. Take a look at https://github.com/emilk/egui/issues/996 for some examples of how others have styled egui, or try out https://app.rerun.io/
Styling is done with `ctx.set_style`, but creating a nice style isn't very easy at the moment (basically you'll have to tweak constants in code, and then recompile). I'm working on making it easier as we speak though!
-
Rust for Embedded Systems: Current State, Challenges and Open Problems
Nothing is wrong with that, it’s rather a workaround, ultimately I am trying to have one language only including the UI too (been playing with egui),so I don’t have to use JavaScript.
https://github.com/emilk/egui
-
We sped up time series by 20-30x
FWIW, I opened an issue: https://github.com/emilk/egui/issues/4046
-
Immediate Mode GUI Programming
That's fair. I don't have experience with other immediate mode libraries. It's good to hear that it's not an intrinsic limitation
https://github.com/emilk/egui?tab=readme-ov-file#layout Here the author discusses the issue directly. They note that there are solutions to the issue, but that they all come with (in their opinion) significant drawbacks.
For my use case, if I have to do a lot of manual work to achieve what I consider behavior that should be handled by the framework, then I don't find that compelling and am inclined to use a retained mode implementation.
- Egui: Immediate mode GUI in Rust on web and native
-
Ask HN: What software do you use for IoT devices and server
It totally depends on what IoT and what purpose, for example:
IIoT/PLC/industrial automation: most likely you will have to use vendors software, most if the time it’s crap, and a mix of several tech stacks like MSSQL/C#/C++
Sensors and such: depends on what are you building or using the sensors: the protocol mostly is MQTT, and if you would store it in a db postrrsql, elasticsearch, surreldb, influxdb among the most I used.
Robots/drones: on what I build, I use protobuf/grpc for performance and cross-language and direct linux socket io, and where needed websocket but mostly for any web interaction rather than the protocol itself. The tech stack for those, the embedded side is up to you or sometimes based on the sdk you are dealing with, the backend/frontend however, I used to use go/nodejs and for frontend svelte or a simple js library/framework, but recently I’m shifting and redoing everything in rust, embedded, backend and frontend (using something like egui https://github.com/emilk/egui).
When it comes to IoT, I try as much as possible to stay away from python unless you are scripting something else done in go/c++/rust, look at python as a glorified bash script, it’s useful for that or other data science work, but not in IoT.
Same goes with other tech you mentioned, it might suit one case but not another, for example, MQTT is good for sensor IoT type, but good luck controlling a drone with it, mongodb might be great to store a fleet of robots with its access credentials and such, but if you try to use it to store realtime data, it might not perform as expected, and so on.
-
GUI library for fast prototyping
AFAIK the Rust equivalent to C++'s Dear ImGui is egui.
-
Rerun 0.9 – a framework for visualizing streams of multimodal data
The creator of Rerun (Emil Ernerfeldt) also created egui [1], an immediate GUI library for Rust. The library is similar to Dear ImGui but it is written in Rust and can be used for desktop and web apps (compiles to WASM and uses WebGL, demo [2]). Desktop apps can target OpenGL (does not display correct colors on macOS, does not work in VirtualBox on Windows) or WGPU (uses native APIs for each platform, works without any problems, but the binary is a big larger).
[1] https://github.com/emilk/egui
-
Textual Web: TUIs for the Web
> [...] you can build UIs that are snappy and keyboard driven.
That's not an advantage that is exclusive to TUIs; after all, you're running your TUI inside a graphical application that emulates a terminal. (Unless you're rocking an actual VT102, in which case I bow down to you.)
In fact there's an entire class of applications that are extremely snappy and keyboard driven, by their very nature: games.
Some people have taken to writing GUI apps like you'd write a game, and the effects range from OK to fantastic. Check out Lagrange (https://gmi.skyjake.fi/lagrange/), AppManager (https://tildegit.org/solene/AppManager), Dear ImGUI (https://github.com/ocornut/imgui), egui (https://github.com/emilk/egui), and many others.
What are some alternatives?
rocket-auth-login - Authentication and login processing for Rust's Rocket web framework. Demonstrates a working example of how to authenticate users and process login as well as how to handle logging out.
iced - A cross-platform GUI library for Rust, inspired by Elm
xargo - The sysroot manager that lets you build and customize `std`
imgui - Dear ImGui: Bloat-free Graphical User interface for C++ with minimal dependencies
proc-macro-crate - `$crate` in procedural macros.
tauri - Build smaller, faster, and more secure desktop applications with a web frontend.
mini-redis - Incomplete Redis client and server implementation using Tokio - for learning purposes only
druid - A data-first Rust-native UI design toolkit.
parquet2 - Fastest and safest Rust implementation of parquet. `unsafe` free. Integration-tested against pyarrow
slint - Slint is a declarative GUI toolkit to build native user interfaces for Rust, C++, or JavaScript apps.
cargo-expand - Subcommand to show result of macro expansion
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]