Filters, hmmm? A good idea, but as you mention, it doesn't
solve the problem of having a function called every time an
eventIn occurs (a field or event is set). The filter approach
would be useful, if we would do some sort of runtime type
checking.
One could try to use ROUTEs. For every user defined prototype
one routes every eventIn to a Script node inside the PROTO
or a global one. But what about standard nodes. Could we
define
PROTO Transform [ ... ] { Transform { } ROUTE ...}
or should we define
PROTO NewTransform [ ... ] { Transform { } ROUTE ... }
and replace all occurrences of Transform in
"the rest of the world" by NewTransform. If this
works we could really implement the extensions
on top of VRML 2.0 using Java Scripting or
JavaScript Scripting only.
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
---------------------------------------------------------------