Isolation of Bevy-independent code

[ClydeHobart]

Is it at all possible to restructure things such that the egui functionality isn't as tethered to the bevy ECS model? I would like to utilize this crate in a bevy project, but to to me it seems more natural for this inspection functionality to basically consist of:

fn inspect<I: Inspectable>(i: &I, ui: &mut egui::Ui) -> bool;

fn inspect_mut<I: Inspectable>(i: &mut I, ui: &mut egui::Ui) -> bool;

The base intended use case for this is just to modify my app's preferences, which lives in a ResMut, not a component.

I understand this constitutes a large change, and it probably makes more sense for any result of this change to exist as a fork rather than a direct change to this repo.

[ClydeHobart]

Upon closer inspection, this appears to be implemented. Apologies for the distraction.