[x3d-public] both -children and -value or @value shouldn't be allowed

Don Brutzman brutzman at nps.edu
Sat May 28 17:36:37 PDT 2016

On 5/28/2016 5:32 PM, Don Brutzman wrote:
> From: Roy Walmsley <roy.walmsley at ntlworld.com>
> Hi,
> Thanks, Don, for your observations. Yes, I agree with copying to the list.
> A further thought is that when we have an SFNode field (such as -geometry and -appearance in the Shape node) there is no such content of "adding nodes". Instead, the dynamic is "set value". Adding or removing nodes only applies to an MFNode field, exemplified by the -children field of the Group node, where we also have addChildren and removeChildren inputOnly fields.
> This particular discussion is limited to "field" definitions for Script and prototypes as well as "fieldValue" definitions in ProtoInstance. It is confusing to use a "-children" property for an SFNode field. While we have reasons, are they of sufficient stature to outweigh the confusion? Well worth discussion.
> Roy

Yes interesting... that points in multiple directions, include Scene Access Interface (SAI), so there are a lot of constraints also.

There aren't too many parent nodes that have this situation in the JSON Encoding... we'll have to look at each one carefully to see if a better general pattern is possible.

all the best, Don
Don Brutzman  Naval Postgraduate School, Code USW/Br       brutzman at nps.edu
Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA   +1.831.656.2149
X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman

More information about the x3d-public mailing list