Skip to content

eframe use egui-winit for both native and web #2023

Open
@luiswirth

Description

@luiswirth

I believe that eframe should use egui-winit for both native and web. eframe should in my opinion be like my old crate eww (egui + winit + wgpu) (doesn't has to be wgpu). Meaning that eframe is only a wrapper around a platform crate (winit) and a renderer crate (wgpu, glium or glow).

This would streamline the egui ecosystem a lot I believe.
Currently the step from eframe to a custom integration is still quite big. This would hopefully make this process a lot easier.
This could probably also avoid code duplication in eframe as you wouldn't have to handle wasm support separately as winit would do it for you.

As mentioned in discord I got my own egui + winit + wgpu integration running on wasm. I know it's way to early to now make the switch to only using winit. But I think this goal is worth pursuing. I'll first provide an example like you @emilk asked on discord for #1755.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions