[x3d-public] Proposed Standard additions. MFStringSequencer and MFNodeSequncer

Joe D Williams joedwil at earthlink.net
Mon Sep 11 12:03:03 PDT 2023


https://mitra.biz/vrml/vrml2/sgi_design_15jan96.html . It gives specific reasons for the design and abilities of ROUTEs which I think are still valid.

Right, the way read it was can't just replace the TO field of a ROUTE, I have to replace the entire ROUTE. 
Same with MF field, if I want to update just one SF value, I have to send the entire MF field (?). 
Thanks,
Joe

-----Original Message-----
From: Vincent Marchetti <vmarchetti at kshell.com>
Sent: Sep 11, 2023 8:31 AM
To: X3D-Public <x3d-public at web3d.org>
Subject: Re: [x3d-public] Proposed Standard additions. MFStringSequencer and MFNodeSequncer

I don't want to discourage anyone from trying any idea in programming, or even discuss potential design of a system which take the current X3D as a jump off point for a much different type of architecture, but I judge that making the ROUTE statements in a scene description modifiable via events. should be far over the horizon for the X3D development and maintenance team, and to be blunt should be pursued in a separate forum such as a github project or Slack channel.

We have several X3D viewers which are open source and lend themselves to being forked and modified to allow modifying the ROUTEs in real time, but these projects should be identified as no longer X3D viewers but a different (possibly much better, I allow) 3D authoring system.

I refer anyone to an interesting document on the design of VRML 2, this document is at https://mitra.biz/vrml/vrml2/sgi_design_15jan96.html . It gives specific reasons for the design and abilities of ROUTEs which I think are still valid.

Vince Marchetti


> On Sep 11, 2023, at 11:14 AM, Joe D Williams wrote:
>
> Great, another way to be able to do without scripting. AddChild, remove child, addroute removeroute.
> Joe
>
> -----Original Message-----
> From: GPU Group
> Sent: Sep 11, 2023 7:01 AM
> To: X3D Graphics public mailing list
> Subject: Re: [x3d-public] Proposed Standard additions. MFStringSequencer and MFNodeSequncer
>
>
> Or rely on integerSequencer to generate integer index, and have a packed/contiguous list:
>
>
> StringSwitch - inputOnly SFInt32 set_index, outputOnly SFString value_changed, field MFString values
>
> NodeSwitch - inputOnly SFInt32 set_index, outputOnly SFNode value_changed, field MFNode values?
>
> Benefit, can generate more node types as needed with fewer lines of code.
>
> Or could combine into one giant FieldChoice node with fields MFNode node_values, MFString string_values, MFDouble, MFFloat, MFTime, MFImage, MFMatrix3f ...
>
> and outputOnly node_changed, string_changed, double_changed, float_changed, time_changed, image_changed, matrix3f_changed output fields,
>
> and when set_index, it outputs any SF that are within the corresponding MF range?
>
> Benefit: only one new node needed.
>
> -Doug
>
>
> On Sun, Sep 10, 2023 at 11:36 PM John Carlson wrote:
> We can do this with SAI by adding and removing routes. But the question is, can we do it declaratively, without script?
>
> John
>
> On Mon, Sep 11, 2023 at 12:23 AM John Carlson wrote:
> Say I want to take a [0,1] fraction key and map it to an MFString keyValue. How do I do that in X3D?
>
> This might be used for alternating Text nodes, or ROUTEs (as nodes), see below.
>
> Also, can I take a similar key fraction and map to keyValue MFNodes?
>
> I realize that Switch plus and ScalarInterpolator would satisfy the latter.
>
> I’m not clear on how to do the former. This would be key to sending events to ROUTEs, changing the from/to node names and fields.
>
> This seems like a very powerful feature! I just don’t know how to route SFString events to route statements. Is there an alternative?
>
> Maybe I should create an Uber X3D? Can we add DEF and name to ROUTEs, and make them first class nodes?
>
> I’m not sure how performant this would be, or even how implementable.
>
> It’s probably an idea to throw in the trash! It’s derived from trying to reduce source code size.
>
> Thanks!
>
> John
>
>
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org


_______________________________________________
x3d-public mailing list
x3d-public at web3d.org
http://web3d.org/mailman/listinfo/x3d-public_web3d.org





More information about the x3d-public mailing list