Make a UI-framework-agnostic core?

[nicoburns]

I would be interested in using this from other Rust GUI frameworks (Dioxus Native). Would you be open to making the core crate UI-framework agnostic, with the egui integration split into a separate crate?

Some notes (how I think this would be implemented):

• Some egui dependencies are types from emath or ecolor. Those dependencies could probably be retained, with the import switched to import directly from emath or ecolor
• Walkers calls egui::Context::request_repaint() and load_texture (tiles.rs) this could be hidden behind a trait or callback
• The egui map widget (map.rs) would probably just move into the egui integration crate. Other integrations would need to implement this logic themselves.
• Abstracting the vector tile drawing code (mvt.rs) is where most of the work would be

[podusowski]

This idea was floating in my mind since the very beginning, but I haven't got any strong motivation to actually bring it to life. So yes, I'd be very open to going into this direction.

There are parts of the rendering code that already uses lyon. I suppose this could be extended to cover all the primitives and use wgpu directly (for which I think egui gives some backdoor too).

[multimeric]

I have a simpler use case, namely to just render the maps to images or video which I'm guessing lyon can do easily.