Peder Blekken wrote:
>
> I think it's a good idea to use the API from TGS'
> SoIntersectionDetectionAction. If you do that, people can alternate
> between using Coin, SGI Inventor and TGS Inventor.
Yes, you're right. I guess if we need extra or modified functionality we
can make our own extensions to that.
>
> : What I've done is use the LGPL SOLID [...]
>
> I haven't done any research on Intersection detection algorithms, so I
> cannot comment on whether this is a good choice or not. Have you read the
> discussions on the UNC Collide Research Group web page?
>
> http://www.cs.unc.edu/~geom/collide/index.shtml
Yes, I've now read it. The papers on SOLID refer to these approaches,
and make performance comparisons. The differences are not very
significant. Also, as far as I know, there are not that many (i.e. 1 or
2) free software collision detection packages, and SOLID is the only one
with significant scientific analysis behind it.
[SoPath additions explained]
Thanks! This is what I was looking for. I've made a quick implementation
of your comments, and it seems to work correctly. I'll try to convert it
into a SoIntersectionDetectionAction as soon as I have some free time.
>
> : If we can implement something similar to the
> : SoIntersectionDetectionAction, I think it should be added to the SGI
> : LGPL Open Inventor library. I'm not sure if the maintainers have thought
> : about things like this, maybe you have some comments (Jonathan?)? I'm also
> : not sure about the relation between the Coin library and the SGI library,
> : is a merge planned or something like that?
>
> No merge is planned between Coin and SGI Inventor. We'll always try to
> be API compatible though, so if you write an extension, it should be no
> problem to use it in both Coin and SGI Inventor.
>
> Peder
I just now read the licensing discussion on the Coin page, and I now see
the reason. As you mention though, I guess it will be no problem to use
everything interchangeably.
Johan
|