Elias Naur bc2c3db43e op/clip,gpu: move approximation of complex strokes to op/clip.Op.Add ...

Before this change, the two renderers both had special case code for
approximating strokes they don't support natively. This change moves
that conversion to clip.Op.Add, for several reasons:

- The compute renderer no longer need fallback logic and caches for
  strokes it doesn't support.
- The approximation logic is slow. Moving it to clip.Op.Add will not
  speed it up, but will make the cost easier to spot in profiles. Until all
  strokes are supported natively, users can use macros to cache
  expensive strokes.
- Reduced garbage: Op.Add takes an op.Ops anyway, and can use that for
  storing the approximated stroke outline.

Signed-off-by: Elias Naur <mail@eliasnaur.com>

2021-03-23 19:37:45 +01:00

..

clip_test.go

op/clip: don't accept open Paths for Outline

2021-03-11 08:57:27 +01:00

clip.go

op/clip,gpu: move approximation of complex strokes to op/clip.Op.Add

2021-03-23 19:37:45 +01:00

doc.go

op/clip: split clip operations into its own package

2019-11-09 19:07:00 +01:00

shapes.go

op/clip: optimize zero corner radius in RRect if pixel-aligned

2021-03-16 19:00:47 +01:00

stroke.go

op/clip,gpu: move approximation of complex strokes to op/clip.Op.Add

2021-03-23 19:37:45 +01:00