[x3d-public] Requirements for X3DV4+, event handling among multiple browsersonsame page

[John Carlson]

Is not specifying a selector in X3DOM what makes polyscoping of the scenegraph difficult?   Can I provide more that one DOM root for a single scenegraph?  Seems possible?

Thoughts?

John

Sent from Mail for Windows 10

From: John Carlson
Sent: Monday, March 4, 2019 4:47 PM
To: X3D Graphics public mailing list; X3D Graphics member mailing list
Subject: RE: Requirements for X3DV4, event handling among multiple browsersonsame page

>Might I suggest tagging events with the browser selector and URL?

I use URL when I want to load more than one URL into a browser (just to confound things).

So URL is probably NOT necessary for X3Dv4.  Only selector.   X_ITE already supports/requires selector for JS at least

An example of where x3dom fails, I think, is when two X3DOM browsers have the same DEF value for a node, and you are accessing the DEF through DOM scripting.  Should we leave this up to the DOM script to differentiate browsers, essentially anyone who wants to support dual X3DOM browsers are required to use id’s, which make DEFs unique? Or require selectors from the start (we know better than you)?

Go X3DOM!

John



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20190304/043cfef1/attachment.html>