On Mon, Mar 10, 2014 at 11:38 AM, Justin Novosad <[email protected]> wrote:
> > > > On Mon, Mar 10, 2014 at 2:14 PM, Rik Cabanier <[email protected]> wrote: > >> On Mon, Mar 10, 2014 at 11:07 AM, Joe Gregorio <[email protected] >> >wrote: >> >> > >> >> > What part is slow, the decoding and re-encoding, or is just always the >> > encoding step >> > that is slow? >> > >> >> It's decoding/re-encoding of an already constructed path. >> > > Can't the implementation just perform that work lazily the first time the > path is rasterized, and retain the cached result for subsequent use of the > path object? > At usage time, the path could be retargeted to a new backend. I don't think that should be done as a cached copy since that would require too many resources. I will see if this is an acceptable solution for mozilla.
