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

Re: [whatwg] Questions regarding Path object

From: Elliott Sprehn <esprehn@chromium.org>
Date: Mon, 11 Nov 2013 15:19:35 -0800
Message-ID: <CAO9Q3iLXhb51=Q3H4ApwFD_Vx5T5Kap83W9_=o=OUJceFBPHuA@mail.gmail.com>
To: Dirk Schulze <dschulze@adobe.com>
Cc: Juriy Zaytsev <kangax@gmail.com>, Dean Jackson <dino@apple.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>, Elliott Sprehn <esprehn@gmail.com>, Ian Hickson <ian@hixie.ch>
On Mon, Nov 11, 2013 at 2:52 PM, Dirk Schulze <dschulze@adobe.com> wrote:

> ...
>
>
> 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.
>
> No.

Then I object to us shipping this in Chrome. Bleeding on the global scope
with such a generic name ignoring all the other reasonable uses of the word
Path is not good for the platform. It's not forward thinking, and it's
confusing for developers.

Why is your one use case more important than FilePath, URLPath and MapPath?
Why do all the other APIs get prefixes and yours doesn't?
- E
Received on Monday, 11 November 2013 23:20:42 UTC

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