GPU Backend: Resource model refactor #310
Draft
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 the start of refactoring pax-pixels and the engines RenderContext trait from this model:
to this model:
exact API pending. The goal of this is to not need to re-tesselate/re-upload image data to the GPU for each draw, but only on significant changes.
Next Steps:
pax-pixels/src/render_context
look like this:change the RenderContext trait (in
pax-runtime-api/src/lib.rs
) to allow for the create/draw API, implement it for the CPU backend (inpax-runtime/src/engine/piet_render_context.rs
). Convert all drawing primitives to use this new API. Convert the pax-pixels render_context API by braking methods like the above into two, and implement the trait for the GPU backend (inpax-runtime/src/engine/pax_pixels_render_context.rs
).Other features still missing from pax-pixels: