<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">John,<br>
      <br>
      In Cobweb, all X3D nodes are not DOM elements. I know this to be
      the case because there are structural and node name conflicts with
      HTML. So what is really being discussed here is Andreas' extension
      to Cobweb. I feel that this is an important distinction to make
      because someone getting just Cobweb would not have DOM access. I
      encourage Cobweb to bring Andreas' extensions into its code.<br>
      <br>
      I agree that preprocessing X3D Script into HTML JavaScript is a
      very viable path forward for legacy content, though I don't think
      people will create new content in that manner. Making everything
      look and act like HTML is the big goal and challenge.<br>
      <br>
      There are significant differences between the event models in DOM
      and X3D. It is more than creation of new events or event handlers.<br>
      <br>
      The requirement to use Proxys needs to be very carefully
      considered. For example Chrome only provides full support in V49
      -- Released in March 2016. Many corporate environments lock down
      their desktops and only slowly make changes. For example, how many
      computers in the US and UK were hit by the WannaCrypt virus on
      computers running Windows XP?<br>
      <br>
      Leonard Daly<br>
      <br>
      <br>
      <br>
    </div>
    <blockquote type="cite"
cite="mid:CAGC3UEmC2VJd_hvzh6xjpMAw33itq2S-LBzEKwZq19vTvF7g3A@mail.gmail.com">
      <div dir="auto">Leonard, you can support the Script tag by
        preprocessing it into JavaScript.   You don't need eval, you
        need something like browserify to preprocess your Scripts into
        JavaScript scripts.   What is left undone is the X3D event
        model, work needs to be done there, but Andreas has shown a way
        forward with the "outputchange" event I believe.   Proxies are
        used for JavaScript events.
        <div dir="auto"><br>
        </div>
        <div dir="auto">Drink the koolaid.  It tastes good.  Use Cobweb,
          you might like it.</div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">John</div>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Jun 14, 2017 10:16 AM, "Leonard
          Daly" <<a href="mailto:Leonard.Daly@realism.com"
            moz-do-not-send="true">Leonard.Daly@realism.com</a>>
          wrote:<br type="attribution">
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div text="#000000" bgcolor="#FFFFFF">
              <div class="m_-9109728504233873042moz-cite-prefix">I keep
                harping on this because no one has yet shown me how this
                is going to happen. <br>
                On page 8 of the notes, item (6): "In principle, all
                nodes in the standard, including scripts and prototypes,
                can be supported."<br>
                <br>
                The X3D Standard specifies that the node is called
                "Script" and contains children tags.<br>
                HTML has a node called "script" without children tags.<br>
                <br>
                1) I do not see how the X3D Standard can be supported
                "in principle" or "in practice" to meet the requirements
                of the statement.<br>
                <br>
                2) HTML scripts are global and have access to the entire
                DOM. #5 states that nodes appear in the DOM, so from an
                HTML script I can modify all nodes in the DOM, including
                X3D ones -- this would include X3D Script nodes if a way
                was found to include it.<br>
                <br>
                3) All scripts in the HTML page occupy the same
                namespace (that is global in scope). From an X3D Script
                (if one was able to exists), I could access all parts of
                the page, including other scripts, including possibly
                non-X3D scripts.<br>
                <br>
                This is not integrating X3D into HTML; but elbowing
                aside an X3D bubble within the HTML space. If X3D is
                going to be integrated with the DOM, then really
                integrate it with the environment. If not, then stop
                using integrating and use something like "X3D space in
                the HTML document"<br>
                <br>
                <br>
                Leonard Daly<br>
                <br>
                <br>
                <br>
                <br>
                <br>
                On 6/13/2017 4:41 PM, Andreas Plesch wrote:<br>
              </div>
              <blockquote type="cite">
                <div dir="ltr"><br>
                  <div class="gmail_extra">
                    <div class="gmail_quote">
                      <blockquote class="gmail_quote" style="margin:0 0
                        0 .8ex;border-left:1px #ccc
                        solid;padding-left:1ex"> During the Web3D 2017
                        Conference in Brisbane Australia,<br>
                        <br>
                                <a
                          href="http://web3d2017.web3d.org/program"
                          rel="noreferrer" target="_blank"
                          moz-do-not-send="true">http://web3d2017.web3d.org/pro<wbr>gram</a><br>
                        <br>
                        the following presentation was given:<br>
                        <br>
                                The Future of X3D<br>
                                Roy Walmsley and Don Brutzman<br>
                                How will the X3D standard adapt to HTML5
                        and virtual and augmented reality on the web?<br>
                        <br>
                        Presentation<br>
                        <a
href="http://www.web3d.org/sites/default/files/page/X3D%20Version%204/FutureOfX3D.pdf"
                          rel="noreferrer" target="_blank"
                          moz-do-not-send="true">http://www.web3d.org/sites/def<wbr>ault/files/page/X3D%20Version%<wbr>204/FutureOfX3D.pdf</a><br>
                        <br>
                        Detailed notes<br>
                        <a
href="http://www.web3d.org/sites/default/files/page/X3D%20Version%204/FutureOfX3dWeb3d2017June7.pdf"
                          rel="noreferrer" target="_blank"
                          moz-do-not-send="true">http://www.web3d.org/sites/def<wbr>ault/files/page/X3D%20Version%<wbr>204/FutureOfX3dWeb3d2017June7.<wbr>pdf</a><br>
                        <br>
                        Photograph by Paul Grimm showing off the
                        incredible venue at Queensland University of
                        Technology (<a href="http://qut.edu.au"
                          rel="noreferrer" target="_blank"
                          moz-do-not-send="true">qut.edu.au</a>) for
                        Web3D 2017:<br>
                        <a
href="http://www.web3d.org/sites/default/files/image/wg/X3D%20Version%204/PresentationPanoramaFutureOfX3dPaulGrimm20170607_135611.1600x492.jpg"
                          rel="noreferrer" target="_blank"
                          moz-do-not-send="true">http://www.web3d.org/sites/def<wbr>ault/files/image/wg/X3D%20Vers<wbr>ion%204/PresentationPanoramaFu<wbr>tureOfX3dPaulGrimm20170607_<wbr>135611.1600x492.jpg</a><br>
                        <br>
                        These links are maintained on the following key
                        page:<br>
                        <br>
                                X3D Version 4<br>
                                <a href="http://www.web3d.org/x3d4"
                          rel="noreferrer" target="_blank"
                          moz-do-not-send="true">http://www.web3d.org/x3d4</a><br>
                        <br>
                        Twitter announcement:<br>
                        <a
                          href="https://twitter.com/Web3DConsortium/status/874662520270708737"
                          rel="noreferrer" target="_blank"
                          moz-do-not-send="true">https://twitter.com/Web3DConso<wbr>rtium/status/87466252027070873<wbr>7</a><br>
                        <br>
                        All questions, dialog and insights are welcome. 
                        This presentation distills much effort and
                        hopefully provides a helpful basis for
                        continuing progress.</blockquote>
                    </div>
                    <br>
                  </div>
                  <div class="gmail_extra">Thanks for sharing this
                    thoughtful presentation. The sketch of an integrated
                    event model is particularly interesting and I may
                    redraw it in an attempt to learn about its workings.<br>
                    <br>
                  </div>
                  <div class="gmail_extra">The sketch is also
                    interesting as it must have come as something of a
                    relief to an audience listening to what must have
                    been the most text heavy presentation at a meeting
                    on 3d graphics ;)<br>
                    <br>
                  </div>
                  <div class="gmail_extra">-Andreas<br>
                  </div>
                  <div class="gmail_extra"><br>
                     <br>
                    <br>
                    <br>
                    <br>
                  </div>
                  <div class="gmail_extra"><br>
                    <br>
                  </div>
                </div>
                <br>
                <fieldset
                  class="m_-9109728504233873042mimeAttachmentHeader"></fieldset>
                <br>
                <pre>______________________________<wbr>_________________
x3d-public mailing list
<a class="m_-9109728504233873042moz-txt-link-abbreviated" href="mailto:x3d-public@web3d.org" target="_blank" moz-do-not-send="true">x3d-public@web3d.org</a>
<a class="m_-9109728504233873042moz-txt-link-freetext" href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" target="_blank" moz-do-not-send="true">http://web3d.org/mailman/<wbr>listinfo/x3d-public_web3d.org</a>
</pre>
              </blockquote>
              <p><br>
              </p>
              <div class="m_-9109728504233873042moz-signature">-- <br>
                <font
                  class="m_-9109728504233873042tahoma,arial,helvetica
                  m_-9109728504233873042san m_-9109728504233873042serif"
                  color="#333366"> <font size="+1"><b>Leonard Daly</b></font><br>
                  3D Systems & Cloud Consultant<br>
                  LA ACM SIGGRAPH Chair<br>
                  President, Daly Realism - <i>Creating the Future</i>
                </font></div>
            </div>
            <br>
            ______________________________<wbr>_________________<br>
            x3d-public mailing list<br>
            <a href="mailto:x3d-public@web3d.org" moz-do-not-send="true">x3d-public@web3d.org</a><br>
            <a
              href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org"
              rel="noreferrer" target="_blank" moz-do-not-send="true">http://web3d.org/mailman/<wbr>listinfo/x3d-public_web3d.org</a><br>
            <br>
          </blockquote>
        </div>
      </div>
    </blockquote>
    <p><br>
    </p>
    <div class="moz-signature">-- <br>
      <font class="tahoma,arial,helvetica san serif" color="#333366">
        <font size="+1"><b>Leonard Daly</b></font><br>
        3D Systems & Cloud Consultant<br>
        LA ACM SIGGRAPH Chair<br>
        President, Daly Realism - <i>Creating the Future</i>
      </font></div>
  </body>
</html>