[x3d-public] MFPath revisited.

[John Carlson]

Original MFPath description.  I’m guessing people want to pass an MFPath to
an SAI function, instead of declaring a field type.

Perhaps using one or two MFPaths in a ROUTE would be best of all, and it
would be declarative as well.

John

---------- Forwarded message ---------
From: <yottzumm at gmail.com>
Date: Sun, Apr 16, 2017 at 10:56 PM
Subject: Proposal for new fieldTypes, MFPath (MFField)
To: x3d at web3d.org <x3d at web3d.org>


I am proposing a new Field type, MFPath  which is a path (similar to CSS
Selectors, XPath, JSONPath, etc) of indexes or keys into the scenegraph.
MFPath is a string based (space or other delimiter separated) list of
SFString’s and SFInt32’s.  The SFString's are used to set/get fields out of
SFNodes, and the SFInt32’s are used to get/add/replace children in
MFNodes.   SFPaths are used on nodes high in the scenegraph.



I assume we would also have an SFPath (SFField) which would be either an
SFString or a SFInt?



Would a better name be MFField?



As motivation, I have posted code to the public list which shows use of
this kind of type in a very simple route, but using MFStrings (well
something like an MFString).  It’s not final yet, but there’s potential.



A simple workaround is to make the SFInt’s into SFString’s, then use
MFStrings.



Would this cause a major heartache in the compiled languages?  Perhaps a
union would work?



I think the idea is to create different languages for paths in the long run.



Just an idea.



John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20251019/960439f2/attachment.html>