blue_engine_egui 0.5.0

egui library for Blue Engine
# Blue Engine egui plugin

This is a plugin that adds [egui]( support to the [Blue Engine](

## Getting started

To get started, create a new struct that will contain your GUI code. For our example:

struct Counter {
    count: u16

Then We'll implement the `Gui` trait of the plugin:

impl Gui for MyGUI {
    // This is the starting point for your UI code, it passes almost all variables of the engine as well
    fn update(
        // for accessing the values
        &mut self,
        // We can add underscore to ones we don't use, so they won't emit warnings
        _window: &mut blue_engine::Window,
        _renderer: &mut blue_engine::Renderer,
        _objects: &mut std::collections::HashMap<&'static str, blue_engine::Object>,
        _camera: &mut blue_engine::Camera,
        _input: &blue_engine::InputHelper,
        _plugin_data_storage: &mut std::collections::HashMap<&'static str, Box<dyn std::any::Any>>,
        ui: &blue_engine_egui::egui::Ui,
    ) {
        /* Your UI code goes here */

And finally your EGUI code:

// Create a new egui window to contain the UI
blue_engine_egui::egui::Window::new("Counter Window").show(ui, |ui| {
    // Add a text to display the counter
    ui.text(format!("The count is at: {}", self.count));
    // + 1 per click
    if ui.button("Add 1").clicked() {
        self.count += 1;

One more steps is left to be done to have the plugin working. We need to initialize the plugin before update loop:

let gui_context = blue_engine_egui::EGUI::new(&engine.event_loop, &mut engine.renderer, Box::new(MyGui {count: 0}));

This will essentially initializes the egui and create things required to run the plugin. The engine will then run it twice, once before everything else to fetch all inputs and events, and then during render, so that it displays the GUI. And all that's left, is to add the plugin to the engine:


Congrats now you have a working GUI!

## Style Block

*The guide will come soon, it's cool I promise!*

## Examples

Check the [examples]( folder for potential UIs and as template for your new projects.

## Dependency justification

* `blue_engine`: Used obiously for exporting some components and struct declrations required to design the API
* `egui-wgpu`: Used to assist in applying egui to wgpu graphics backend. Which is same graphics backend used in Blue Engine.
* `egui-winit`: Support for Winit windowing. Which is same windowing system used in Blue Engine.
* `egui`: The egui itself, required to obtain components and declrations for api design.