[x3d-public] Requirement for v4. one X3D element per Frame

[John Carlson]

Can we autogenerate an incrementing browser # and stick it into the outer scenegraph as a div id?

John

Sent from Mail for Windows 10

From: John Carlson
Sent: Thursday, January 31, 2019 9:05 PM
To: Don Brutzman; Vincent Marchetti; Richard F. Puk; X3D Graphics public mailing list
Subject: Requirement for v4. one X3D element per Frame

>Can we think of it in terms of IFrames?  An Iframe per canvas? Then put one X3D element per IFrame

>>"The main requirement for this comes from scripting...how to access the right field if it’s loaded more than once.

>>Which may be a good reason not to support fields in Scripts or Scripts at all.” (no Scripts)

>“I think the selector in question is on the scene or X3D element.   I am not sure if my code fully supports inlines, plus I am reusing the scene (allowed???).

>>Yet another reason not to support regular JavaScript in X3D.” (Scripts)

Suggestion for V4:  Only support one X3D element per frame/iframe, otherwise we are schizophrenic (They’re coming to take me away, oh no!).  0, or 2 or more X3D elements are allowed, but not supported.

Are there other ways of seeing this? The use case is showing a scenegraph 4 times, twice as X3DOM, twice as X_ITE, twice as JS/DOM and twice as XML, trying to script various elements in scene.

Can someone see a fault in this?  Should I start porting my code over to this to see any difficulties?  I know IFrames are difficult, but I think we should show our multicanvas apps with multiframes.

Almost bedtime.

John


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20190131/94246b51/attachment-0001.html>