#ui #layout #bevy #lunex #bevy-lunex


Blazingly fast path based modular layout system built on top of Bevy ECS

9 releases

0.0.9 Nov 20, 2023
0.0.8 Nov 17, 2023
0.0.6 Sep 15, 2023
0.0.3 Aug 27, 2023

#208 in Game dev

Download history 35/week @ 2023-08-20 44/week @ 2023-08-27 39/week @ 2023-09-03 57/week @ 2023-09-10 48/week @ 2023-09-17 37/week @ 2023-09-24 17/week @ 2023-10-01 12/week @ 2023-10-08 15/week @ 2023-10-15 33/week @ 2023-10-22 33/week @ 2023-10-29 105/week @ 2023-11-05 101/week @ 2023-11-12 84/week @ 2023-11-19 61/week @ 2023-11-26 73/week @ 2023-12-03

356 downloads per month
Used in 2 crates


2.5K SLoC


Version 0.0.9 RELEASED!

v0.0.9 is very close to the release of v0.1.0!

Blazingly fast path based modular layout engine built on top of Bevy ECS. It calculates layout from user-defined rectangle positions and percentages. Works for all aspect ratios. Uses retained style UI. (It may develop into full-fledged UI lib in the future)

Note: I'm currently super busy with school, so the development during the school year is rather slow

=== Showcase ===


Gif Cyberpunk gif

^ A recreation of Cyberpunk UI in Bevy. (Source code here).

=== Description ===

Bevy-Lunex is a layout engine based on defining and managing rectangles. It strives to be clean, simple and intuitive to the user. The most prominent use case is to use it as a "building brick" for your own user interface.

The core of this library is pure math layout engine, meaning no styling or rendering is currently included. That's where you come in. You can use the library to hook your own components and custom rendering to make it look exactly the way you want (May change in the future into full-fledged UI lib :D ).

By attaching entities to coordinates returned by Bevy Lunex, you can abstract complex positioning logic away from you. Take a look at these examples:

Currently the most up-to-date practices and workflow can be found in the Bevypunk project.

=== Workflow ===


--- Usage ---

Due to the nature of Rust, we had to come up with a unique way how to manage data. We decided to implement hierarchy tree structure, which is used in UNIX file system.

All data is stored in a master struct, called "UiTree", which manages all layout data. The "UiTree" is composed of "UiBranches", where each branch represents a rectangle and they can be nested inside each other. "Widgets" are custom smart pointers containing a "path" to the corresponding nested "UiBranch". "Widgets" are components and are spawned as entity.

When needed, the "Widget" can fetch "UiBranch" inside the "UiTree" and return a mutable borrow. From the borrow you can modify the layout data, thus changing the behaviour and the result of the rectangle calculations taking place. This is the way to get around the Rust's borrow checker.

> UI
  |-> Main_menu
  |    |-> Background
  |    |-> Board
  |    |    |-> Logo
  |    |    |-> Buttons
  |    |    |    |-> Continue
  |    |    |    |-> New_Game
  |    |    |    |-> Load_Game
  |    |    |    |-> Settings
  |    |    |    |-> Credits
  |    |    |    |-> Additional_Content
  |    |    |    |-> Quit_Game

^ This is a "UiTree" structure printed out in a terminal. Each item displayed here is "UiBranch". Look for example at the "Board" branch, in which are nested "Logo" and "Buttons" branches.

--- Tree creation ---

First, create a "UiTree" struct that will hold all the layout data managed recursively. We also need to specify the generic, which is optional field each widget can have and store data in.

let mut tree: UiTree<MyData> = UiTree::new("UI");

--- Layout definition ---

To create a new "Widget" in the root directory you pass in the "UiTree", specify widget properties and the function returns the smart pointer.

let widget: Widget = WindowLayout::empty()
    .with_size_rel(80.0, 80.0)
    .build_as(&mut tree, "widget")?;

--- Logic binding ---

Once you have the "Widget" created, you can pass it to an entity as a component together with other components like "Image". Here we use "ImageElementBundle", which is the same as "SpriteBundle", but has extra fields for "Widget" and "Element". Element component is used when you need to attach a visual entity to a widget, like text or image.

        Vec2::new(1280.0, 250.0)),

In this example, we also passed another component called "ButtonHighlightEffect", which we will define in the next section.

--- Logic definition ---

To add logic to your "Widgets", you use Bevy systems. In this example, we will create a system that will tint the sprite to a certain colour if a cursor hovers over the "Widget" First we define the component with color data. Then we define the system that will query "UiTree", "Cursor" and our components. Add the logic and we are done.

pub struct ButtonHighlightEffect (pub Color);

fn button_highlight_effect_update<T:Component + Default>(
    trees: Query<&UiTree<T>>,
    cursors: Query<&Cursor>, 
    mut query: Query<(&Widget, &mut Sprite, &ButtonHighlightEffect)>
) {
    for tree in trees {
        for (widget, mut sprite, color) in &mut query {

            if !widget.fetch(&tree).unwrap().is_visible() {return;}

            let mut trigger = false;
            for cursor in &cursors {
                if widget.contains_position(&tree, &cursor.position_world().invert_y()).unwrap() {
                    trigger = true;

            if trigger{
                sprite.color = color.0;
            } else {
                sprite.color = Color::WHITE;

--- Last ---

Don't forget to add the system to the app.

.add_systems(Update, button_highlight_effect_update::<T>)

You need to spawn the "UiTree" we created in the first step as an entity so we can query for it.


--- Layout options ---

There are 3 main layout options to pick from. With their combination, you can define any setup. They are:

  • RELATIVE || Defined from 2 points, as % of the parent container.
  • SOLID || Defined as a ratio of width and height. Will scale to fit or fill parent.
  • WINDOW || Defined as a point + width and height. Same as RELATIVE.

By nesting branches of these 3 types, you can precisely define the position and layout behaviour.

=== Versions ===

Bevy Bevy Lunex
0.12.0 0.0.7 - 0.0.9
0.11.2 <= 0.0.6

=== Contributing ===

Any contribution submitted by you will be dual licensed as mentioned below, without any additional terms or conditions.

=== Licensing ===

Released under both APACHE and MIT licenses, for the sake of compatibility with other projects. Pick one that suits you the most!


~1.5M SLoC