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

Re: [whatwg] Questions regarding Path object

From: Dirk Schulze <dschulze@adobe.com>
Date: Mon, 11 Nov 2013 14:52:11 -0800
To: Elliott Sprehn <esprehn@gmail.com>
Message-ID: <8F6FA8D5-D384-40D7-999D-719E9336BA9A@adobe.com>
Cc: Juriy Zaytsev <kangax@gmail.com>, Rik Cabanier <cabanier@gmail.com>, Jürg Lehni <lists@scratchdisk.com>, "whatwg@lists.whatwg.org" <whatwg@lists.whatwg.org>, Simon Pieters <simonp@opera.com>, Dean Jackson <dino@apple.com>, Ian Hickson <ian@hixie.ch>

Sent from my iPhone

On Nov 12, 2013, at 6:18 AM, "Elliott Sprehn" <esprehn@gmail.com<mailto:esprehn@gmail.com>> wrote:

On Mon, Nov 4, 2013 at 9:14 AM, Rik Cabanier <cabanier@gmail.com<mailto:cabanier@gmail.com>> wrote:
On Mon, Nov 4, 2013 at 2:07 AM, Jürg Lehni <lists@scratchdisk.com<mailto:lists@scratchdisk.com>> wrote:

> Thinking more about this discussion, I had an idea for an approach that
> would avoid such future clashes all together:
> Instead of exposing constructors, why not simply expose the methods that
> create them?
> There already are such functions for gradients:
> ctx.createRadialGradient()
> ctx.createLinearGradient()
> Wouldn't it have been more aligned with this existing API also to have a
> ctx.createPath() ?

The SVG WG would like to start using the 'Path' object for its objects as
well. We'd like this to be a generic object that can be used by other parts
of the web platform.
It would be strange to require a canvas context just to create pathh.

I'd like to again say I don't think this thing should be called Path. Lots of other things have "Paths", like maps, file systems, urls, why does the drawing one get to take the global namespace?

Given that there's a bunch of new objects with Drawing as the prefix, I think we should name this DrawingPath like DrawingStyle and friends.



- E
Received on Monday, 11 November 2013 22:52:36 UTC

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