W3C home > Mailing lists > Public > public-geometryapi@w3.org > July 2013

Re: things often done in geometrical applications

From: Doug Schepers <schepers@w3.org>
Date: Mon, 08 Jul 2013 04:10:00 -0400
Message-ID: <51DA73D8.8040704@w3.org>
To: Rik Cabanier <cabanier@adobe.com>
CC: Jon Williams <jon@shovemedia.com>, "public-geometryapi@w3.org" <public-geometryapi@w3.org>
Hi, Rik-

On 7/8/13 1:11 AM, Rik Cabanier wrote:
>
> thanks for starting the page!

Thanks for joining the CG!


> I agree that it would be very useful to find the intersection of 2
> paths. Most often you'd like to find if a path intersects a rectangle
> or bounding box (ie for hit testing) so maybe this could be another
> function I'm not sure if we need to create a routine that does this
> for stroked paths. Rather, I would like to see a routine that gives
> you the "shape" of a stroked path and use that to find
> intersections.

I agree with that approach.

This also suggests that we should include the various joins, unions, 
exclusions, and intersections described in the Vector Effects spec as 
API operations. Many of those will duplicate planned functionality 
anyway, so exposing them via an API is not much more work.


> We should also start small. There's no need to tackle everything and
> we can always add more later. Personally, I would like to build upon
> the path routines in canvas and make them compatible with SVG.

Agreed.


[1] 
http://dev.w3.org/SVG/modules/vectoreffects/master/SVGVectorEffectsPrimer.html
[2] http://dev.w3.org/SVG/modules/vectoreffects/master/SVGVectorEffects.html

Regards-
-Doug
Received on Monday, 8 July 2013 08:10:09 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:51:20 UTC