W3C home > Mailing lists > Public > public-webevents@w3.org > January to March 2011

Re: Draft minutes: 22 February 2011 call

From: Olli Pettay <Olli.Pettay@helsinki.fi>
Date: Mon, 21 Mar 2011 18:15:29 +0200
Message-ID: <4D8779A1.40407@helsinki.fi>
To: "public-webevents@w3.org" <public-webevents@w3.org>
CC: chase.douglas@canonical.com
On 02/22/2011 07:16 PM, Arthur Barstow wrote:
>     <scribe>  ACTION: olli investiage various angle-related work e.g.
>     InkML, CSS, SVG, ... [recorded in
>     [24]http://www.w3.org/2011/02/22-webevents-minutes.html#action02]
>
>     <trackbot>  Created ACTION-17 - Investiage various angle-related work
>     e.g. InkML, CSS, SVG, ... [on Olli Pettay - due 2011-03-01].


CSS supports several unit types for angles[1].
They are used for transformations.

InkML[2] uses deg and rad. But InkML uses angles
for pen tilt and orientation. So not quite what
we're doing.

SVG might be closest to our case, since it has ellipses[3],
and other shapes. I guess the initial decision for
radiusX/Y in the events was based on the SVG syntax.
In SVG that is enough, since one can use rx/ry and
then the generic rotate(deg) using the transform.
But we need to have that all that data in the events
(if we want to support all this).
So, should we perhaps have this all working close to
SVG?
Having the current radiusX/Y and also
rotationAngle (in deg (-90, 90])?



-Olli


[1] http://www.w3.org/TR/css3-values/#angles
[2] http://www.w3.org/TR/InkML/
[3] http://www.w3.org/TR/SVG/shapes.html#EllipseElement
Received on Monday, 21 March 2011 16:16:03 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 21 March 2011 16:16:10 GMT