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 so that existing rendering libraries/binaries can re-use nannou/lyon heavy lifting and migrate to it in progression.
As an example, alacritty already has its rendering context, but the rendering of polygons and paths for decorations (i.e. background effects) could use nannou's logic.
While the vertices from certain shapes work without this PR (i.e.
draw.ellipse()
), when one attempts to use adraw.path()
, this is behind several private layers: the Draw.state
, the.intermediary_state
and finally the.path_event_buffer
where the vertices are located for bezier curves and such.By exporting these immutable references of the state, other projects can start calling
draw.<shape>()...
and the project can have a function similar tonannou::draw::renderer::Renderer::fill()
in which the draw commands are drained and primitives are rendered in the existing project rendering context.Signed-off-by: Seb Ospina [email protected]