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

[John Carlson]

X_ITE has a wrapping tag around the X3D.

Thanks,

John

Sent from Mail for Windows 10

From: Leonard Daly
Sent: Friday, February 1, 2019 1:43 PM
To: x3d-public at web3d.org
Subject: Re: [x3d-public] Requirement for v4. one X3D element per Frame

John,


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.

There would be a problem having more than one possible interpreter for X3D. Each interpreter would try to interpret the same code without knowing that the other one was running. This is independent of any duplication of tag 'id' attributes. You could have each interpreter only look for code inside a unique (to them) tag. For example
<x3dom>
  <x3d>
    :
    :
  </x3d>
</x3dom>
and
<x-ite>
  <x3d>
    :
    :
  </x3d>
</x-ite>

Though this seems awkward and kludgy.
Each X#D viewer application may choose (or not) to support multiple instances per page. That would be more a matter of handling their own internal data stores.
Note that for augmented reality applications using the ImmersiveWeb specification, the browser will enforce that the application runs full-screen. If these are loaded as iFrames, then the necessary permissions will need to be granted to the iFrame in order for that application to display.

Leonard Daly



 
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
 


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

-- 
Leonard Daly
3D Systems & Cloud Consultant
LA ACM SIGGRAPH Past Chair
President, Daly Realism - Creating the Future 

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