Draft: Add Phyre interop layer, allow game asset loading#119
Draft
Draft: Add Phyre interop layer, allow game asset loading#119
Conversation
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 is a draft PR. Do not merge.
Resolves #55.
We want to enable the use of game assets in ImGui flows. The only permissible way to do so is to load them at runtime, as they must not be shipped with mods. For this to work, the Phyre engine must be called to pry open its custom asset containers.
Phyre types are generally self-describing. That is to say, Phyre classes have 'class descriptors', which contain information about the type such as its name and layout. By inspecting these class descriptors, we can somewhat operate generically over Phyre types.
Where names for classes and/or fields are given, they are sourced from RTTI metadata available in the executables themselves.