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

[Andreas Plesch]

The reason for the X_CITE X3DCanvas wrapper around the X3D element was
that the X3D element is already defined by the XML encoding but
additional attributes and styling was needed. Also it makes it clear
that the X3D content on the page is shown using a HTML canvas element.

It is true that X3D is not concerned about how to make sure that scene
access occurs to the intended X3D browser (window, X3DCanvas or X3D
element, iframe). It is up to the system using a X3D browser.
Generally that should be not a problem since the system wanting to
access a X3D browser, is the same system that creates the X3D browser
in question and therefore has a way to remember a reference to that
X3D browser. The system may be a human or a machine.

If the system creates multiple browsers, it still knows which browsers
it created. For example, it could add an unique 'id' attribute to each
X3D element to help it remember the browsers. Or it could use
document.querySelectorAll('X3D')[index] to select a browser by their
order on the web page.

Probably I am missing something,

-Andreas

> Date: Fri, 1 Feb 2019 13:45:46 -0600
> From: John Carlson <yottzumm at gmail.com>
> To: Leonard Daly <Leonard.Daly at realism.com>,  "x3d-public at web3d.org"
>         <x3d-public at web3d.org>
> Subject: Re: [x3d-public] Requirement for v4. one X3D element per
>         Frame
> Message-ID: <5c54a1e9.1c69fb81.868ee.3552 at mx.google.com>
> Content-Type: text/plain; charset="utf-8"
>
> 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.html>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>
>
> ------------------------------
>
> End of x3d-public Digest, Vol 119, Issue 8
> ******************************************

-- 
Andreas Plesch
Waltham, MA 02453