bevy_editor_pls VS krABMaga

I think one part that makes this extra obvious is bevy UI and the attempts at an editor. I remember when https://github.com/jakobhellermann/bevy_editor_pls came along and I was very excited, but since then nothing has really happened on the editor front. Not that I need an editor personally, but what I find disappointing and telling is that this whole thing has been basically halted because of bevy's idea of having UI in the ECS.

Also, there is this Bevy plugin https://github.com/jakobhellermann/bevy_editor_pls/

It's on of the primary initiatives right now. Games are not developed by only programmers, we're well aware of that. There are a few ongoing existing ecossytem level efforts like bevy_editor_pls. For an official editor, we're just lacking the UI tooling to fully flesh it out right now. Like Godot, Bevy's dogfooding it's own UI solution for the official editor, but it's not quite there yet. Bevy isn't alone in this. There's a smorgasbord of ongoing work in the Rust for UI space, and there's quite a bit of greenfield efforts to develop a data-oriented or ECS style approach to UI layouting and management. Once we have this a bit more hammered down, it's just a matter of time before an official editor becomes available.

It is something we've been building toward for awhile. We've been focused on core systems like the renderer and ecs for awhile now, but we're finally at the point where we can start moving up the stack.

We will be focusing on scenes, asset workflows, ui, and the editor from here on out (with scenes, asset workflows, and UI being the focus for the next release).

I'd like to have some sort of editor MVP by the end of the year.

Until then, there are community efforts like: https://github.com/jakobhellermann/bevy_editor_pls

P.S. There is an effort to make an editor for Bevy if you're interested, though it's not complete.

For now though, bevy_editor_pls is a surprisingly useful third-party prototype.

I wrote a thesis for my bachelor's regarding the development of an agent-based simulation framework in Rust where I managed the visualization side. The project takes inspiration from other frameworks such as MASON (in particular for the architecture), NetLogo, Agent.jl and others. I initially developed the visualization subsystem with Amethyst, after my thesis Amethyst was discontinued and, since I was already following Bevy since it went public and it looked like it was gaining a lot of momentum, I refactored our framework to switch to Bevy. Our project is open source: https://github.com/krABMaga/krABMaga . Being my first approach to Rust and my first serious greenfield project, I think there are a lot of parts which can be improved, but I was able to get by with my extremely limited knowledge of both Rust and Bevy and obtain decent results. The things I loved the most of Bevy was the low amount of boilerplate code needed, the WASM+WebGL support which allowed me to easily let guests run simulations from our github.io site (https://krabmaga.github.io/) at near native (sequential) performance and, just like the whole Rust ecosystem, the friendliness of the community. Even though I bothered quite a bit on the Discord server since the documentation wasn't the clearest for me back when I started (Bevy 0.5), both the team members and users always led me a hand. I also think the ECS approach is extremely useful for our usecase, by defining agents as entities with the Agent component, along with a system which acts as an event loop by executing a simulation step and triggering the agents' behaviour rules.

The framework includes the possibility to visualize simulation using bevy-engine on local or via browser exploiting wasm technology. You can play with some examples on our website! Also take a look at our github page, the framework is completely open-source and we would be pleased to receive your comments!