Discussion about declaratively modifying routes. #1

coderextreme · 2023-09-11T20:58:57Z

Tag yourself in this issue to get emails. Add a comment.

Note that this is enough of a modification that forking may be considered. Or at least, development off the main branch.

coderextreme · 2023-09-11T21:00:52Z

@create3000 says:

It is not all official SAI but X_ITE has internally and official these route functions:

X3DExecutionContext.addRoute (sourceNode, sourceField, destinationNode, destinationField) : X3DRoute
X3DExecutionContext.deleteRoute (route)
X3DExecutionContext.getRoute (sourceNode, sourceField, destinationNode, destinationField) : X3DRoute
X3DExecutionContext.getRoutes () : RouteArray
X3DBrowser.addRoute (sourceNode, sourceField, destinationNode, destinationField)
X3DBrowser.deleteRoute (sourceNode, sourceField, destinationNode, destinationField)

1 and 2 are standard.
3 is non-standard, but could be useful.
4 is the same as ‚routes‘ property.
5 and 6 are legacy functions from VRML ages, but I like them too.

Discussing declarative syntax can also be done in an issue(s), this has a lot of advantages. Think you all know GitHub issues.

coderextreme · 2023-09-11T21:04:26Z

So my thought is that an editor or authoring system already provides ways to update route fields. Can we take the route features of an authoring system, and make them available in XML or VRML syntax?

create3000 · 2023-09-11T21:04:37Z

With DOM integration you can find routes like you would do find any HTMLElement, with native DOM methods or maybe jQuery:

https://github.com/create3000/Library/blob/ba2a1e79276923e2c0b15933a5c6995256cdc5b6/Tests/Browser/DOMIntegration/inline_route.xhtml

coderextreme · 2023-09-11T21:09:58Z

We’re also hoping to make this feature available in castle-engine and view3dscene. So portability of scripts is an issue. This is not really an SAI/DOM discussion, but yes, SAI or DOM will implement the features we do to the scene, so SAI modications are probably first

coderextreme · 2023-09-11T21:20:39Z

From my original post, I suggested that a fraction from [0,1] would map to integers which would map to a position in an MFString. The MFString would potentially update a ROUTE.

coderextreme · 2023-09-11T23:06:53Z

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, 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 is.

coderextreme · 2023-09-11T23:09:23Z

I’m also thinking of a TextInterpolator where one one SFString morphs into another …

coderextreme · 2023-09-12T00:08:31Z

So there’s some discussion about using an id attribute (CSS) to update a route. So one would use CSS instead of a sequencer or interpolator to change values instead of SAI or DOM. Hmm!

coderextreme · 2023-09-12T03:47:41Z

For reference, here’s the code bloat I’m trying to reduce. I’ve got 4 files of this. https://github.com/coderextreme/jaminate/blob/main/Jaminate/app/src/main/javascript/takes.John.txt

the timings in each file are slightly different.

coderextreme · 2023-09-12T03:54:13Z

Here’s what I generate the 4 files with:

https://github.com/coderextreme/jaminate/blob/main/Jaminate/app/src/main/javascript/takes.js

(I know, lots of commented out code)

coderextreme · 2023-09-12T03:57:10Z

I only need the characters, moves per character, and times per character arrays to generate the code bloat. I’m looking for a quicker load time. https://github.com/coderextreme/jaminate/blob/main/Jaminate/app/src/main/javascript/John.json

coderextreme · 2023-09-12T03:58:37Z

If there’s an easier way to do this, I’m all ears

coderextreme · 2023-09-12T04:01:49Z

One solution may be to write 2 scripts, one like takes.js and the other in castle script

create3000 · 2024-12-13T09:36:32Z

What about this prototype? Set names of nodes and field names, then toggle enabled:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE X3D PUBLIC "ISO//Web3D//DTD X3D 4.0//EN" "https://www.web3d.org/specifications/x3d-4.0.dtd">
<X3D profile='Interchange' version='4.0' xmlns:xsd='http://www.w3.org/2001/XMLSchema-instance' xsd:noNamespaceSchemaLocation='https://www.web3d.org/specifications/x3d-4.0.xsd'>
  <head>
    <component name='Scripting' level='1'/>
  </head>
  <Scene>
    <ProtoDeclare name='Route'>
      <ProtoInterface>
        <field accessType='inputOutput' type='SFBool' name='connected'/>
        <field accessType='inputOutput' type='SFNode' name='sourceNode'/>
        <field accessType='inputOutput' type='SFString' name='sourceField'/>
        <field accessType='inputOutput' type='SFNode' name='destinationNode'/>
        <field accessType='inputOutput' type='SFString' name='destinationField'/>
      </ProtoInterface>
      <ProtoBody>
        <Script DEF='RouteScript'>
          <field accessType='inputOutput' type='SFBool' name='connected'/>
          <field accessType='inputOutput' type='SFNode' name='sourceNode'/>
          <field accessType='inputOutput' type='SFString' name='sourceField'/>
          <field accessType='inputOutput' type='SFNode' name='destinationNode'/>
          <field accessType='inputOutput' type='SFString' name='destinationField'/>
          <IS>
            <connect nodeField='connected' protoField='connected'/>
            <connect nodeField='sourceNode' protoField='sourceNode'/>
            <connect nodeField='sourceField' protoField='sourceField'/>
            <connect nodeField='destinationNode' protoField='destinationNode'/>
            <connect nodeField='destinationField' protoField='destinationField'/>
          </IS>
<![CDATA[ecmascript:

let route;

function initialize ()
{
   set_connected ();
}

function set_connected ()
{
   const scene = Browser .currentScene;

   if (connected)
   {
      if (!sourceNode || !sourceField)
         return;

      if (!destinationNode || !destinationField)
         return;
      
      route = scene .addRoute (sourceNode, sourceField, destinationNode, destinationField);
   }
   else if (route)
   {
      scene .deleteRoute (route);
   }
}
]]>
        </Script>
      </ProtoBody>
    </ProtoDeclare>
  </Scene>
</X3D>

coderextreme · 2024-12-13T10:17:04Z

I found Browser.addRoute and Browser.deleteRoute. Work great. AFAIK, BS Contact does not like global variables. Especially ones starting with let. I may have an old version. John

…

On Fri, Dec 13, 2024 at 3:36 AM Holger Seelig ***@***.***> wrote: What about this prototype? Set names of nodes and field names, then toggle enabled: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE X3D PUBLIC "ISO//Web3D//DTD X3D 4.0//EN" "https://www.web3d.org/specifications/x3d-4.0.dtd"> <X3D profile='Interchange' version='4.0' xmlns:xsd='http://www.w3.org/2001/XMLSchema-instance' xsd:noNamespaceSchemaLocation='https://www.web3d.org/specifications/x3d-4.0.xsd'> <Scene> <ProtoDeclare name='Route'> <ProtoInterface> <field accessType='inputOutput' type='SFBool' name='enabled'/> <field accessType='inputOutput' type='SFString' name='sourceNode'/> <field accessType='inputOutput' type='SFString' name='sourceField'/> <field accessType='inputOutput' type='SFString' name='destinationNode'/> <field accessType='inputOutput' type='SFString' name='destinationField'/> </ProtoInterface> <ProtoBody> <Script DEF='RouteScript'> <field accessType='inputOutput' type='SFBool' name='enabled'/> <field accessType='inputOutput' type='SFString' name='sourceNode'/> <field accessType='inputOutput' type='SFString' name='sourceField'/> <field accessType='inputOutput' type='SFString' name='destinationNode'/> <field accessType='inputOutput' type='SFString' name='destinationField'/><![CDATA[ecmascript:let route;function initialize (){ set_enabled ();}function set_enabled (){ if (!sourceNode) return; if (!sourceField) return; if (!destinationNode) return; if (!destinationField) return; const scene = Browser .currentScene; if (enabled) { route = scene .addRoute (scene .getNamedNode (sourceNode), sourceField, scene .getNamedNode (destinationNode), destinationField); } else if (route) { scene .deleteRoute (route); }}]]> </Script> </ProtoBody> </ProtoDeclare> </Scene> </X3D> — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFMJ53DIDH65DP6KIUDOWD2FKTDLAVCNFSM6AAAAABTRS6EMCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBQHE4TIMBVGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

coderextreme changed the title ~~Discussion about modifying routes.~~ Discussion about declaratively modifying routes. Sep 11, 2023

coderextreme mentioned this issue Sep 11, 2023

Crossposting feature request. Declaratively modifying routes castle-engine/castle-engine#532

Closed

create3000 added the question Further information is requested label Dec 13, 2024

create3000 added the solved Question is solved label Dec 13, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Discussion about declaratively modifying routes. #1

Discussion about declaratively modifying routes. #1

coderextreme commented Sep 11, 2023 •

edited

Loading

coderextreme commented Sep 11, 2023 •

edited by create3000

Loading

coderextreme commented Sep 11, 2023

create3000 commented Sep 11, 2023

coderextreme commented Sep 11, 2023 •

edited

Loading

coderextreme commented Sep 11, 2023

coderextreme commented Sep 11, 2023 •

edited

Loading

coderextreme commented Sep 11, 2023

coderextreme commented Sep 12, 2023

coderextreme commented Sep 12, 2023 •

edited

Loading

coderextreme commented Sep 12, 2023

coderextreme commented Sep 12, 2023 •

edited

Loading

coderextreme commented Sep 12, 2023

coderextreme commented Sep 12, 2023

create3000 commented Dec 13, 2024 •

edited

Loading

coderextreme commented Dec 13, 2024 via email

Discussion about declaratively modifying routes. #1

Discussion about declaratively modifying routes. #1

Comments

coderextreme commented Sep 11, 2023 • edited Loading

coderextreme commented Sep 11, 2023 • edited by create3000 Loading

coderextreme commented Sep 11, 2023

create3000 commented Sep 11, 2023

coderextreme commented Sep 11, 2023 • edited Loading

coderextreme commented Sep 11, 2023

coderextreme commented Sep 11, 2023 • edited Loading

coderextreme commented Sep 11, 2023

coderextreme commented Sep 12, 2023

coderextreme commented Sep 12, 2023 • edited Loading

coderextreme commented Sep 12, 2023

coderextreme commented Sep 12, 2023 • edited Loading

coderextreme commented Sep 12, 2023

coderextreme commented Sep 12, 2023

create3000 commented Dec 13, 2024 • edited Loading

coderextreme commented Dec 13, 2024 via email

coderextreme commented Sep 11, 2023 •

edited

Loading

coderextreme commented Sep 11, 2023 •

edited by create3000

Loading

coderextreme commented Sep 11, 2023 •

edited

Loading

coderextreme commented Sep 11, 2023 •

edited

Loading

coderextreme commented Sep 12, 2023 •

edited

Loading

coderextreme commented Sep 12, 2023 •

edited

Loading

create3000 commented Dec 13, 2024 •

edited

Loading