- From: Jon Williams <jon@shovemedia.com>
- Date: Mon, 8 Jul 2013 11:19:53 -0400
- To: "public-geometryapi@w3.org" <public-geometryapi@w3.org>
I too want intersections, and A) if those intersections have 2D area, I want to be able to dig down into the child verticies. B) if the intersection is between two paths, I need the subsystem to do the curve-curve, curve-line etc intra-segment interpolation and the API should tell me the point indexes in the originals between which the intersection(s) were found, so that if a point insertion is required, I don't have to manually reverse engineer that detail. And a pony. :j On Jul 8, 2013, at 4:10 AM, Doug Schepers <schepers@w3.org> wrote: > 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 15:20:24 UTC