bevy-website VS egui

There is a Rust tool named `generate-release` within the website repository[0]. It handles interacting with the Github API to get a list of significant changes, breaking changes, and contributors. (The main Bevy repository has pull request labels for all of these, so this is pretty easy.)

[0]: https://github.com/bevyengine/bevy-website

https://github.com/bevyengine/bevy-website/issues/1097 Yep, on our wishlist and will be added :)

We'd like to open the floodgates on Bevy Book development asap. This taking so long has largely been my fault ... I've been overly protective of the Bevy Book while also not giving it the attention it deserves. Here is our current plan: https://github.com/bevyengine/bevy-website/issues/623#issuec..., which I'd like to execute during the next cycle.

Latest Progress: https://github.com/bevyengine/bevy-website/pull/550/files

I do want previews though.

API docs, examples and the revised book: https://github.com/bevyengine/bevy-website/pulls?q=is%3Aopen...

Strongly agreed on the need for better introductory material; the existing book is extremely incomplete.

> I don't have this clear. Are 5/6 teams actually building commercial games with Bevy, or they just planning to do it in the future? This is a crucial distinction.

I know of 2 released commercial projects, the CAD team, a few indie devs who have started and 3 or so small studios who are looking to start. There's a little thread in the Discord where I've rounded folks up: [Bevy in production](https://discord.com/channels/691052431525675048/995713618526...).

We also do some real cleverness around split borrows in order to enable automatic system parallelism. This draft book page goes into more concrete details :)

Can do

I used the unofficial bevy cheatbook a lot to learn the ropes. Everyone on the discord is super friendly and helpful and the official documentation is being updated, you can check out the PRs on the book branch

Thank you for linking your project—that looks really cool! I saw you also implemented a pan-and-zoom area. We are currently working on moving Rerun's implementation to egui [0], so maybe keep an eye on that.

It would be super cool to have layered graph drawing in (Sugiyama-style) in Rerun too. The tricky–but super interesting–challenge that we face is that our layout implementations need to be consistent across timestamps if the underlying structure of the graph changes, which is why we initially chose a force-based layout approach. There, the time-varying aspect is handled naturally by the simulation.

The very interactive nature of Rerun also poses more restrictions on the implementation of our algorithms: re-layouts ideally need to be fast, to produce visualizations quickly, especially when scrubbing the timeline.

I still hope we can rid you of some of the todos ;).

[0](https://github.com/emilk/egui/pull/5505)

Yeah, I knew I was in for some onoz when I saw "compiled to WebAssembly and rendered with WebGL". In their defense, it's stunning that any text operations work at all

Also, "There is no DOM, HTML, JS or CSS" is some uh-huh given the considerable amount of silliness involved in view-source:https://www.egui.rs/

One of these projects, which is built using Rust, is egui. In this article, we’ll see how we can build a simple, cross-platform GUI application with it.

Cross-platform UI development is a total mess with literally zero solutions ticking all the boxes.

If you want to write an app which will target all the major platforms (3 desktops and two mobiles), want a native look and minimal effort for every platform you target, there is nothing apart from QT.

If you drop native look requirement, some small things like https://www.egui.rs/ might work for you.

If you drop the minimal effort requirement, all the webivew based mess might help you but it won't be easy due to multiple reasons.

It allow to edit large json files > 500mb. It is written in rust and use the amazing egui library