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

Re: [whatwg] canvas 2d's ellipse

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Tue, 20 Aug 2013 16:06:38 -0700
Message-ID: <CAAWBYDCsN6sNrefLZDMQ-415o4_J5gBDWM4Hx5c4WJtRk4B0Sw@mail.gmail.com>
To: Ian Hickson <ian@hixie.ch>
Cc: WHATWG <whatwg@whatwg.org>, Rik Cabanier <cabanier@gmail.com>, Robert O'Callahan <robert@ocallahan.org>
On Tue, Aug 20, 2013 at 3:46 PM, Ian Hickson <ian@hixie.ch> wrote:
> On Tue, 30 Apr 2013, Rik Cabanier wrote:
>> I think the API should look like this:
>> void ellipse(unrestricted double x, optional unrestricted double y,
>> unrestricted double radiusX, optional unrestricted double radiusY, optional
>> unrestricted double rotation, optional unrestricted double startAngle,
>> optional unrestricted double endAngle, optional boolean anticlockwise);
>> with the following behavior:
>> - if radiusY is omitted, it's the same as radiusX
>> - if rotation is omitted, it's equal to 0
>> - if startAngle is omitted, it's equal to 0
>> - if endAngle is omitted, it's equal to 0
>> - if anticlockwise is omitted, it's equal to false
> We could do this, sure. How much do people want something like this? Does
> anyone else think it's a good idea?

I can tell you that specifying all of the arguments in SVG's ellipse
path command is rather annoying.  Having good defaults would be a good

Received on Tuesday, 20 August 2013 23:07:24 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:09:23 UTC