-
Notifications
You must be signed in to change notification settings - Fork 1.6k
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FFI-safe UI and related structures #2898
Labels
feature
New feature or request
Comments
I've been wondering how I would go about making a plugins feature for a program I'm making. |
maybe duplicate of #1004 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Consider a program that wishes to enable development of plugins which could render their own UI within the parent app window. A concrete example would be a Digital Audio Workstation (DAG).
This maps well to egui architecture, as the plugin only needs
&mut egui::Ui
for most basic functionality. Passing&egui::Context
as well would enable more, but isn’t necessary for an MVP.The issue here is that Rust doesn’t provide a stable ABI out of the box.
Describe the solution you'd like
Make
egui::Ui
and all arguments of its methodsrepr(C)
and FFI-safe.Describe alternatives you've considered
Additional Context
The abi_stable crate could do most of the heavy lifting AFAICT.
Open questions
The text was updated successfully, but these errors were encountered: