> Yes, and there's already a fairly straightforward path to implementation,
> through the existing Inventor engine mechanisms. I think Besoft is trying
> to do too much with the engines, however, by trying to use them as interfaces
> to interprocess communication (someone correct me if this is wrong).
Ok.
Actually, our scheme doesn't use Inventor engines at all. We have a notion of
"behavioral object", and a class system for such objects.
The system has some subclasses that look something like engines, and
others that look like scripts. The two varieties can be mixed and embedded in each other
freely (and within the scene).
Anyway, see our pages (http://www.besoft.com), particularly the technicnal overview,
for details.
Chris Goad
BE Software
[email protected]