Modularize Editor#186
Open
foxnne wants to merge 49 commits into
Open
Conversation
Phase 3a
7e21a93 to
3248fea
Compare
Allow ABI-version mismatches to reject loading plugin Handle loading config area plugins excersize 3rd party plugin Update build files for sdk
3248fea to
95f3dc2
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR is a large work in progress to discern information about the future of modularizing the editor.
This is the largest change to fizzy since rewriting in DVUI.
As of now, the proof of concept already works, with pending edits to DVUI to add a proxy backend, allowing us to compile individual libraries (plugins) which can be runtime loadable.
Currently, the app is now split into the following:
The editor itself is now often referred to as a shell, as it just reads plugins and renders their contributions to the correct regions.
- Handles rendering tabs and splits
- Basically all the functionality of fizzy originally, but contained to a plugin
- Support image loading and editing, adding supported docs to tabs/splits
- Basic text editing and syntax highlighting
The strategy here is to essentially statically link ALL builtin plugins for the web build. For the native build, we vendor a
pluginsfolder containing the dylibs the editor will read at runtime. We also look for plugins at the config location, so hopefully we can support 3rd party plugins sooner rather than later.Goals