W3C home > Mailing lists > Public > whatwg@whatwg.org > November 2013

Re: [whatwg] CanvasRenderingContext2D with addPath, currentPath

From: Rik Cabanier <cabanier@gmail.com>
Date: Mon, 4 Nov 2013 11:25:53 -0800
Message-ID: <CAGN7qDCM_taya8O2F-sTDQrfEWdv2W6rgP9jH4gx6AFdJ=CxNg@mail.gmail.com>
To: Jürg Lehni <lists@scratchdisk.com>
Cc: "whatwg@whatwg.org" <whatwg@whatwg.org>, Ian Hickson <ian@hixie.ch>
On Mon, Nov 4, 2013 at 1:49 AM, Jürg Lehni <lists@scratchdisk.com> wrote:

> > What's the use case?
> >
> > I intentionally didn't add this to the spec when I was adding the last
> set
> > of path-related features, because it seems entirely redundant with Path
> > objects. I thought we'd want people to move away from using the implicit
> > path, rather than making it more powerful.
> I like this feature a lot. One advantage to not underestimate is the
> amount of effort it takes to change existing code to make use off the new
> Path feature, while staying backward compatible with older browsers that
> don't implement this spec. For example, in Paper.js it took only three
> added lines of code to use cached paths if they exist rather than redrawing
> them each time

Do you think getCurrentPath should return a path in user space or in the
current transformation matrix?
Received on Monday, 4 November 2013 19:26:20 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:13 UTC