> It seems that there are many proposals on various behaviour
> aspects, but not a lot of discussion on collision detection.
> I don't know if some of you consider it a bahaviour as well
> (not me though) but I think it is something that could be
> achieved easier (in terms of specification that is) than
> behaviours and I feel that it is equally important!
CONCEPTUALLY it really is the same as behaviors. The only
difference is that it really needs to be fast (not scripted, well
integrated).
My suggestion for an approach to behaviors which are common and must be
FAST: Get the behavior very standardized and implimentable as scripts.
At this point browser writers, to improve their browser performace,
should internalize the behavior code, allowing it to bypass the API when
accessing the accessable scene-graph and run as fast compiled code.
HOWEVER, I think the general framework for VRML should not limit it to
mearly sharing data representing 3D physical spaces. No reason why the
same standard suite can't be used for whiteboarding and conferencing, etc.
-Braddock
----- http://pcil.ece.jhu.edu/~braddock ----- braddock@jhu.edu -----
"We are here for no purpose, 3209 N. Charles St. Apt. 3A
unless we can invent one. Baltimore, MD, 21218
Of that I am sure." (410) 467-3380
-Kurt Vonnegut, Jailbird (Epilogue)