[whatwg] new constructor method for Path2D
Tab Atkins Jr.
jackalmage at gmail.com
Mon Mar 10 13:03:15 PDT 2014
On Mon, Mar 10, 2014 at 11:38 AM, Justin Novosad <junov at google.com> wrote:
> On Mon, Mar 10, 2014 at 2:14 PM, Rik Cabanier <cabanier at gmail.com> wrote:
>> On Mon, Mar 10, 2014 at 11:07 AM, Joe Gregorio <jcgregorio at google.com
>> > 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?
This is also my question. Given that generating a path for a
particular context isn't a magic bullet *anyway* (because the details
of the context can change), I don't understand why caching isn't the
More information about the whatwg