[x3d-public] Understanding of IS connect for xml...issue for JSON encoding.

[doug sanden]

Yes, you can IS to script fields and protoinstance fields in v3.3

-Doug

more..

Dynamic fields -per-instance like Script, or per type like ProtoInstance- are abstracted to look like normal fields during runtime. That means you can/should-be-able-to IS to them (and ROUTE to them) like they are normal fields. That includes builtin, Script and ProtoInstance fields. Except we know the names and types of builtin  fields a priori, and for dynamic fields we need to describe their types in the scene file. So ideally they are orthogonal / separate issues: declaring dynamic fields, and ISing / ROUTEing to any field dynamic or builtin.

more..

Gotchas:

- early vrml implementations didn't allow static fields ie Field or InputOutput, just events EventIn and EventOut. I think they are allowed in v3.3, or seem to work.






________________________________
From: x3d-public <x3d-public-bounces at web3d.org> on behalf of John Carlson <yottzumm at gmail.com>
Sent: June 30, 2016 9:40 PM
To: X3D Graphics public mailing list
Subject: [x3d-public] Understanding of IS connect for xml...issue for JSON encoding.


My understanding of IS connect is as follows.  For Script nodes, the nodeField refers to a field "name" attribute value.  For regular nodes, the nodeField is an attribute name.  Any other gotchas?  Does ProtoInstance take an IS node?

If the distinction between field and attribute is not there in VRML (is it?), why do we have it in the JSON encoding?  Does it lead to better validation of files?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20160701/ea0ff2db/attachment.html>