You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The recently added canvas (#215) uses CPU rendering via tiny-skia to a cached texture.
Tiny-skia does not support GPU rendering at all; Lyon provides a vaguely similar API and does; see this example.
The objective should be an easy-to-use Lyon Canvas widget over a fixed pipeline (or fixed set of pipelines). This requires an API which doesn't exist in the examples, but could work roughly as follows:
// add to DrawSharedT:// this method tessellates a path, returning some identifier#[cfg(feature = "lyon")]fnlyon_path(&mutself,path: lyon::path::Path, ..) -> PathId;// new trait:#[cfg(feature = "lyon")]pubtraitDrawableLyon:Drawable{fnlyon_instances(&mutself,instances:&[Primitive]);}
It is an open question how flexible the API should be. Note that a custom WGPU pipeline (similar to the Mandlebrot example) can be used where this API insufficient.
The text was updated successfully, but these errors were encountered:
The recently added canvas (#215) uses CPU rendering via tiny-skia to a cached texture.
Tiny-skia does not support GPU rendering at all; Lyon provides a vaguely similar API and does; see this example.
The objective should be an easy-to-use Lyon Canvas widget over a fixed pipeline (or fixed set of pipelines). This requires an API which doesn't exist in the examples, but could work roughly as follows:
It is an open question how flexible the API should be. Note that a custom WGPU pipeline (similar to the Mandlebrot example) can be used where this API insufficient.
The text was updated successfully, but these errors were encountered: