From: Jae-Joon L. <lee...@gm...> - 2008-09-24 18:32:53
|
> > Well merging is obviously better. I wrote YAArrow to support > plain-vanilla annotations. AFAIK, they are used nowhere else, so as > long as we could come up with one arrow class that works with > plain-vanilla and fancy annotations, that would be good. But it may > be easier said than done. These annotation arrows are really helper > classes that are instantiated by higher level functions (eg users most > likely won't be creating them themselves) and since they all have the > basic patch interface, I don't think having a proliferation of them is > the worst thing in the world, though the ideal is to have as few > classes as possible that serve as many cases as possible. > > Thanks. Yes, merging seems better to me too. And it seems that I can slightly tweak the current interface of my class so that it get along well with pre-existing classes. I'll work on the merge and post the patch sometime soon. > > I believe you are looking for the scanline boolean algebra -- search > the antigrain demo page > > http://www.antigrain.com/demo/index.html > > for scanline_boolean.cpp. Of course, we would need to support the > other major backends too.... > I'm not sure if scanline_boolean does what I want (but I have to admit that I haven't looked at its code carefully yet). Do you know if it is possible to stroke along the union of the two paths (this is what I want)? My impression is that scanline thing is for filling the path. Anyhow, I'll take a more look. > > This appears to be LGPL, so we will not be using it in the main distro. > Yes, it's LGPL. And I didn't mean to include it in mpl. Anyhow, I think I'll go with the first method for the moment. Thanks, -JJ |