Expand description
Backend-agnostic interface for writing apps using egui
.
epi
provides interfaces for window management and serialization.
An app written for epi
can then be plugged into eframe
,
the egui framework crate.
Start by looking at the App
trait, and implement App::update
.
Re-exports§
pub use egui;
Modules§
- backend
- You only need to look here if you are writing a backend for
epi
. - file_
storage - File storage which can be used by native backends.
Structs§
- Dummy
Storage - Stores nothing.
- Frame
- Represents the surroundings of your app.
- Icon
Data - Image data for the icon.
- Integration
Info - Information about the integration passed to the use app each frame.
- Location
- Information about the URL.
- Native
Options - Options controlling the behavior of a native window.
- WebInfo
- Information about the web environment (if applicable).
Constants§
Traits§
- App
- Implement this trait to write apps that can be compiled both natively using the
egui_glium
crate, and deployed as a web site using theegui_web
crate. - Native
Texture - Abstraction for platform dependent texture reference
- Storage
- A place where you can store custom data in a way that persists when you restart the app.