Bevy UI Build macros

A collection of macros to speed up the process of defining UIs in bevy.

Bevy version

We do not specify the bevy version we depend on. The reason is mostly that I rely on a personal fork of bevy, and it's a complete hassle to fork every bevy library to make them work with my own fork of bevy.

Since this does nothing else than define macros, there is no compiled code in this crate. the only requirements for the macro to work is that the few bevy symbols we rely on are in scope where the macros are called. The bevy symbols we explicity use are:

bevy::ecs::system::Insert
bevy::math::{Rect::{self, all}, Size::new}
bevy::prelude::Parent
bevy::ui::{entity::NodeBundle, Style, Val::{Percent, Px}}

Macros

The macros are nothing more than wrappers around the struct commonly used when defining bevy UIs.

```rust // unit! -- UNIT -- unit!(10 px); unit!(100 pct); // Equivalent to Val::Px(10.0); Val::Percent(100.0);

// style! -- STYLE -- style! { flexwrap: FlexWrap::Wrap, flexbasis: unit!(90 pct), }; // Equivalent to Style { flexwrap: FlexWrap::Wrap, flexbasis: unit!(90 pct), ..Default::default() };

// size! -- SIZE -- size!(100 pct, 90 pct); size!(90 px, 40 px); // Equivalent to Size::new(Val::Percent(100.0), Val::Percent(90.0)); Size::new(Val::Px(90.0), Val::Px(40.0));

// rect! -- RECT -- rect!(10 px); rect!(5 px, 0 px); rect!(100 pct, 10 pct, 50 pct, 0 pct); // Equivalent to Rect::all(Val::Px(10.0)); Rect { left: Val::Px(5.0), right: Val::Px(5.0), top: Val::Px(0.0), bottom: Val::Px(0.0), }; Rect { left: Val::Percent(100.0), top: Val::Percent(10.0), right: Val::Percent(50.0), bottom: Val::Percent(0.0), };

// buildui! -- BUILDUI -- buildui! { #[cmd(commands)] vertical{size:size!(100 pct, 100 pct)}( horizontal{justifycontent: FlexStart, flexbasis: unit!(10 pct)}( tabsquare[;focus], tabsquare[;focus], tabsquare[;focus] ), columnbox( column;red ) ) } // Equivalent to commands.spawnbundle(NodeBundle { style: Style { size: size!(100 pct, 100 pct), .. vertical.style }, .. vertical }) .withchildren(|cmds| { cmds.spawnbundle(NodeBundle { style: Style {justifycontent: FlexStart, flexbasis: unit!(10 pct), .. horizontal.style }, .. horizontal }) .withchildren(|cmds| { cmds.spawnbundle(tabsquare).insert(focus); cmds.spawnbundle(tabsquare).insert(focus); cmds.spawnbundle(tabsquare).insert(focus); }); cmds.spawnbundle(columnbox) .withchildren(|cmds| { cmds.spawnbundle(column).insert(red) .withchildren(|cmds| { vertical.withchildren(|cmds| { cmds.spawnbundle(selectsquare); cmds.spawnbundle(selectsquare); }); cmds.spawnbundle(NodeBundle { style: Style {flexwrap: Wrap, ..horizontal.style}, .. horizontal }).insert(gray) .withchildren(|cmds| { for _ in 0..12 { cmds.spawnbundle(square).insert(focus); } }); cmds.spawnbundle(NodeBundle { style: Style {flexwrap: Wrap, ..horizontal.style}, .. horizontal }).insert(gray) .withchildren(|cmds| { for _ in 0..8 { cmds.spawn_bundle(square).insert(focus); } }); }); }); }); ```

Changelog

0.2.0
- Breaking: The build_ui! macro now uses [bundle;comp] instead of just a list of components between square brackets. This makes it possible to specify a list of components. This however requires having the semicolon at the beginning of the square brackets if you only want to specify additional components. [;like, this]

License

This is weird. Since this code literally cannot produce distributable binary code, I don't think any of the mainstream license apply. On top of that, I usually license libraries I make with less than 100 lines of code under the WTFPL. But I'll be a good community player and dual license under MIT or Apache 2.0 at your leisure.