<div dir="auto">I am not sure what the hoopla is, as far as I know, vrml scripts work in Cobweb without changing the tagname or Inlines. You just have to load the file with SAI or similar.<div dir="auto"><br></div><div dir="auto">If you want to code x3d just like HTML, good luck. Make a real case for it. I think there are too many examples of stuff not being hard-coded into the browser. While you are worried about X3D in HTML, Three.js will run away with a your cheese. You might argue performance, but I would say move towards shaders.</div><div dir="auto"><br></div><div dir="auto">Quit being whiny babies and work with the technology. If you can't debug scripts right now, you may be able to in the future. Or use Browser.print or console.log. It's old school, but it works.</div><div dir="auto"><br></div><div dir="auto">Working with the technology may allow you to see additional solutions.</div><div dir="auto"><br></div><div dir="auto">I have somewhat working Protos and scripts with X3DOM now (by no means perfect, just one working example :-), because I spent the time in the technology. The key is to look for solutions, not problems.</div><div dir="auto"><br></div><div dir="auto">If you are stuck in the C++ world, work on something like jsasm.js. Yes, I do believe that people are compiling C++ to work in webpages.</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto">John</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mar 28, 2017 1:37 PM, "Leonard Daly" <<a href="mailto:Leonard.Daly@realism.com">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 bgcolor="#FFFFFF" text="#000000">
<div class="m_9041998788609446872moz-cite-prefix">Only have time right now to respond to
the first thing that caught my attention...<br>
<br>
</div>
<blockquote type="cite"><br>
It's not clear that much much recent dialog is penetrating several
portions of your list. For example, SVG also has a script node
that seems to operate just fine in combination with HTML. It
seems prudent to pose interoperability as the baseline goal
requirement, with the corresponding due diligence to compare
pros/cons and implement alternatives. Listing things like "nodes
shall not have name conflicts" and "shall behave as the HTML
element" as end states seems to close off such necessary
consideration of alternative approaches that already exist and can
work.
<br>
</blockquote>
<br>
It has been repeated pointed out that SVG has a script node. It is
called script. SVG is also part of HTML5 and fully integrated into
the DOM. Also SVG's script is a real JavaScript node that is
accessible from outside of the SVG tag set. In order to get X3D
there, X3D would need to be recognized as part of HTML and this
would need to be regular JavaScript element. Based on everything I
did in a quick read (several pages from a Google search of 'SVG
Script') this morning, you can script SVG from inside or outside of
the SVG tag.<br>
<br>
So until X3D becomes fully integrated in HTML and can be solely
scripted through DOM and does not need a JavaScript library to parse
and execute it, there is no point in talking about an X3D Script
node.<br>
<br>
<div class="m_9041998788609446872moz-signature">-- <br>
<font class="m_9041998788609446872tahoma,arial,helvetica m_9041998788609446872san m_9041998788609446872serif" 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">x3d-public@web3d.org</a><br>
<a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" rel="noreferrer" target="_blank">http://web3d.org/mailman/<wbr>listinfo/x3d-public_web3d.org</a><br>
<br></blockquote></div></div>