bytestring-net / bevy_lunex

Blazingly fast path based retained layout engine for Bevy entities, built around vanilla Bevy ECS.
https://bytestring-net.github.io/bevy_lunex/
Apache License 2.0
478 stars 18 forks source link

Request for clarity on 1.0 release plans #17

Closed Qs-Official closed 5 months ago

Qs-Official commented 5 months ago

(Usually there are communities i can go to, but there doesnt seem to be one so sorry if this is the wrong place for this)

I'd like to start contributing, and got really excited about this project, but it seems I picked a weird time. Id like a window into the plans and potential features/differences from the current system to 1.0. If its not all concrete yet, and you'd rather not. Then a peek into whats currently being thought about/lightly worked on

(i dug around and found blueprint_ui but it didnt help my confusion, is this all just frozen until further notice?)

IDEDARY commented 5 months ago

Hello, it is completely fine to ask this here. I'm currently crunching school due to my finals for graduation. That is the reason why the development is rather slow and accidental. But it will only be like this until June. After that I will be as active as I was in the begging of the project.

Lunex 0.1.0 is ~80% done. I have decided on the following crate layout:

All the new code is currently public right here:

Contributions are very appreciated and welcome, but yeah, I agree. It is a weird time, because I'm making very hectic and big changes to the codebase. But I think that the stuff is more or less settled and all I just need to do is add or re-implement functionality.

The reactivity api should look like Bevypunk - main branch. Not the layout declaration, but the logic in components paradigm.

This is old API, but i will move towards COMPONENT only logic as much as much as I can.

commands.spawn((
            lg::Animate::new(),
            lg::AnimateControl::new(0.25, 0.05),
            lg::AnimateColor::new(self.text_color, self.text_hover_color),
            lg::PipeAnimateInputFromTree,
        ));

In the new API I managed to create COMPONENT only layout definition, so if things go well, we will have UI defined from only components, which means, server driven UI or UI hot reloading.

My next goals is to:

I hope I gave you some insights into the Project. If you have any questions, don't hesitate and ask. For quick chat you can contact me on Bevy Discord or DM me @idedary

Qs-Official commented 5 months ago

Thank you for your amazing response!

Good luck with your studies! It takes serious amount of dedication to stay on top of it all, even just on its own, so to work on a project like this even a little alongside that is super impressive to me and worth commending, so tear it up out there!

I'll be looking into the various repos in hopes to be of help in the near future, I love the ideas being explored here and would like to help as much as i can!