But having this powerful dynamic routing mechanisms
with paths the problem is how to prevent errors
when a node required in a path does not exist.
Let's call such a path invalid (and there maybe
other reasons why a path is not valid).
As routing works in VRML 2.0 we would get
an error. I like the way it works in constraint
languages, if a path is not valid nothing
happens, the current action is suspended.
If a node is created and the path
becomes valid, the action is reactivated.
The question is, whether we can implement this
functionality with the Java-Scripting interface
as it is and will it be efficient? In VB2 (Balaguer's system)
there are required, strong and weak constraints. In
analogy we could have required paths, which means
that if a node does not exist or the path
is invalid in some other sense then we would
get an error, whereas strong and weak paths
must not always be valid.
I would like to come to a consensus on this
point and start implementing the extension
as far as we have agreed (CLASSES, INTERFACES,
PATHS). I would then release the implementation for
others to write and test reasonable interface definitions
for the standard nodes of VRML 2.0
Cheers
-- Stephan
---------------------------------------------------------------
Dr. Stephan Diehl Tel.: ++49-681/302-3915
EMAIL: diehl@cs.uni-sb.de WWW: http://www.rw.cdl.uni-saarland.de/private/diehl
---------------------------------------------------------------
There is no place like $HOME
---------------------------------------------------------------