<div dir="ltr">Not too be a hater but I don't think its a good idea to include PROTO's into X3DOM. The VRML/X3D proto spec + scripting interactions is very hard to get cross platform. I spent many years dealing with it and its just too much work. Personally I'd rather see that development time spent elsewhere improving X3DOM. It's very helpful to be able to define your own vocabulary but as it stands PROTO's are not a proven cross platform way to do it. Maybe the other web native routes will have better luck. </div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 13, 2015 at 12:54 PM, Andreas Plesch <span dir="ltr"><<a href="mailto:andreasplesch@gmail.com" target="_blank">andreasplesch@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Indeed, not having a PROTO node is a substantial lack of functionality in the x3dom code base and a loss if compared with standalone x3d browsers. At the risk of misinterpretation, to me it looks like there was conscious decision by the x3dom developers at some early point that the certainly very substantial cost of developing such functionality outweigh the expected benefits. This may have changed by now, x3dom-developers ?<br><div>If not, it follows that there would be a large demand for guidance in terms of documentation, tutorials and perhaps tools on how to convert/translate PROTOs into x3dom compatible js code or custom x3dom nodes. I tried to provide some initial pointers but clearly input by the x3dom group is what is really required.<br></div><div>-Andreas<br></div><div><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 13, 2015 at 3:00 PM, <span dir="ltr"><<a href="mailto:x3d-public-request@web3d.org" target="_blank">x3d-public-request@web3d.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send x3d-public mailing list submissions to<span class=""><br>
<a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:x3d-public-request@web3d.org" target="_blank">x3d-public-request@web3d.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:x3d-public-owner@web3d.org" target="_blank">x3d-public-owner@web3d.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br></span>
than "Re: Contents of x3d-public digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: [X3D-Public] Prototype (Daniel Vera)<br>
2. SSR: server-side rendering (doug sanden)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Fri, 13 Feb 2015 10:31:24 +0000<br>
From: Daniel Vera <<a href="mailto:d.a.vera@warwick.ac.uk" target="_blank">d.a.vera@warwick.ac.uk</a>><br>
To: John Richardson <<a href="mailto:richards@spawar.navy.mil" target="_blank">richards@spawar.navy.mil</a>><br>
Cc: <a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a><br>
Subject: Re: [x3d-public] [X3D-Public] Prototype<br>
Message-ID: <<a href="mailto:54DDD27C.1040900@warwick.ac.uk" target="_blank">54DDD27C.1040900@warwick.ac.uk</a>><br>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"<span class=""><br>
<br>
John,<br>
<br>
Apologies for reviving an old thread, but in my opinion not having<br>
capability similar to VRML protos is indeed a loss of functionality;<br>
<br>
Explanation: I am an engineer (industrial production), not a developer;<br>
VRML PROTO/EXTERNPROTO has allowed our group to build rich 3D based<br>
engineering application using VRML/javascript code only (i.e. without<br>
the need to go in the depth of coding with low level libraries etc.).<br>
<br>
(<a href="https://www.youtube.com/user/FDSvideosFDS/videos" target="_blank">https://www.youtube.com/user/FDSvideosFDS/videos</a>)<br>
<br>
Looking into Andreas links (Box.js code in particular), it seems the way<br>
to go is to define additional X3DOM nodes, but that requires<br>
understanding X3DOM code, which not every class of users wants or has<br>
time to do; In my opinion, X3DOM should match the capability provided by<br>
X3D in defining complex modelling class/object using X3D/javascript<br>
code/syntax only.<br>
<br>
That said, I am open to additional suggestion, discussion or links to<br>
more information!<br>
<br>
Regards, Daniel<br>
<br></span></blockquote></div></div></div></div>
<br>------------------------------------------------------------------------------<br>
Dive into the World of Parallel Programming. The Go Parallel Website,<br>
sponsored by Intel and developed in partnership with Slashdot Media, is your<br>
hub for all things parallel software development, from weekly thought<br>
leadership blogs to news, videos, case studies, tutorials and more. Take a<br>
look and join the conversation now. <a href="http://goparallel.sourceforge.net/" target="_blank">http://goparallel.sourceforge.net/</a><br>_______________________________________________<br>
x3dom-developers mailing list<br>
<a href="mailto:x3dom-developers@lists.sourceforge.net">x3dom-developers@lists.sourceforge.net</a><br>
<a href="https://lists.sourceforge.net/lists/listinfo/x3dom-developers" target="_blank">https://lists.sourceforge.net/lists/listinfo/x3dom-developers</a><br>
<br></blockquote></div><br></div>