Conversation
wow-miley
deleted the
email/pho-3-phosphor-multi-target-renderer-interface
branch
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
1 participant
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.
Implements PHO-3 in phosphor-core by introducing a serializable SimulationFrame/FrameCell model, RenderTarget enum, generic PhosphorRenderer contract, and a hot-swappable RendererRegistry. Adds a common ComposeRenderer output model plus a JVM TerminalRenderer with ANSI output and ~30fps throttling semantics. Includes a MultiTargetRendererExample showing the same frame rendered to terminal and compose targets simultaneously. Enables Kotlin serialization plugin/dependencies and adds targeted tests for frame serialization/round-tripping, registry behavior, compose mapping, terminal output/throttle behavior, and the dual-target example; ./gradlew jvmTest passes.