This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
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.
Another follow up on #9327 and #9541, this time focusing on
RendererFrontend
andRendererBackend
:HeadlessFrontend
and make it the main coordinator for headless rendering. It replacesNodeRendererFrontend
,AsyncRendererFrontend
, andStubRendererFrontend
. It contains aHeadlessBackend
andRenderer
, andOffscreenView
is merged intoHeadlessBackend
. As a result, headless rendering clients only need to manage a single frontend object, instead of coordinating a frontend, a backend, a backend scope, a renderer, and a view.View
intoRendererBackend
. This is a natural followup, since as a result of the previous change, allRendererBackend
implementations also implementedView
, and the one other implementation ofView
did not actually need to do so (OffscreenTexture
, which doesn't need to be used polymorphically).