[x3d-public] cobweb DOM integration

[doug sanden]

if added to SAI SFNode interface, then it might need a parameter: sfnode.getContainerField(parent) since some nodetypes have multiple containerfield targets by fieldname, but usually (Q1. always?) just one  field for a given parent nodetype.
Q2. in an ExternProto scenario, before extern proto is loaded, and no concrete node as first node of protobody, how to determine via a function what is the containerfield its instances should target their parents? Can we put a field 'containerField' or MFString containerFields? Does cobeweb delay instancing extern protos until the extern is loaded and concretized before allowing getContainerField?
Q3. terminology: does 'container' part of containerfield refer to the parent ie parent is container or does it refer to the field ie a field is a container?

________________________________________
From: x3d-public <x3d-public-bounces at web3d.org> on behalf of Andreas Plesch <andreasplesch at gmail.com>
Sent: October 9, 2016 9:00 PM
To: X3D Graphics public mailing list
Subject: Re: [x3d-public] cobweb DOM integration

On Sun, Oct 9, 2016 at 10:35 PM, Andreas Plesch <andreasplesch at gmail.com<mailto:andreasplesch at gmail.com>> wrote:
...
What are other strategies for determining the field in a container node which should (most likely) be set given just the identity of a new node and its containing (parent) node ?


Some more investigating brought to light that cobweb.js already has a node.getContainerField() method which seems to be exactly what I was looking for. Excellent.

The SAI does not have such a function:

http://www.web3d.org/documents/specifications/19777-1/V3.3/Part1/functions.html#t-SFNodeFunctions

Should it be added to the spec. ?

--
Andreas Plesch
39 Barbara Rd.
Waltham, MA 02453



--
Andreas Plesch
39 Barbara Rd.
Waltham, MA 02453