bevy_crossterm
bevy_crossterm copied to clipboard
octotep
Crossterm plugin for the bevy game engine
Checking in to see if there are any future plans to continue development of the bevy_crossterm crate. If not, would there be any possibility of access/ownership transfer for continued development?...
much as the title says the beginning of migration to the latest bevy api is needed. additionally, it would be excellent to develop a consistent workflow of updating in step...
I am new to bevy and rust so idk how useful I can write this issue but I started a rust project with `cargo new` and I cargo added `bevy`...
Primarily updates to be compatible with bevy 0.5, but also: * Updates for IDE file ignores * Added a Makefile for development workflow convenience * Added a .rustfmt file and...
The new API is different and causes required changes in bevy_crossterm.
Wanted to use this with bevy 0.5, so i updated it into a state that at least allows compiling. Gonna need help fixing the examples and cleaning up my code.
Not a bug but a feature suggestion would be to make this work with notcurses, too. It would make an outstanding option for the terminal.
The asset change detection is rough. We have to loop through all asset added/changed events, then loop through ALL entities to see which ones have assets that need to be...
It would be nice to allow parent entities to have a Postition that is then propagated to the children (and so on recursively). One could then easily group and move...