<html><head>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
</head><body style="font-family: Calibri; font-size: 12pt;" 
text="#000000" bgcolor="#FFFFFF"><div style="font-size: 
12pt;font-family: Calibri;"><span style="font-family: Calibri;">John,<br><br>Apologies
 for reviving an old thread, but in my opinion not having capability 
similar to VRML protos is indeed a loss of functionality;<br><br>Explanation:
 I am an engineer (industrial production), not a developer; VRML 
PROTO/EXTERNPROTO has allowed our group to build rich 3D based 
engineering application </span><span><span style="font-family: Calibri;">using
 VRML/javascript code only (i.e. </span></span><span style="font-family:
 Calibri;">without the need to go in the depth of coding with low level 
libraries etc.). <br><br>(<a class="moz-txt-link-freetext" href="https://www.youtube.com/user/FDSvideosFDS/videos">https://www.youtube.com/user/FDSvideosFDS/videos</a>)<br><br></span><span><span>Looking
 into Andreas links (Box.js code in particular), it seems the way to go 
is to define additional X3DOM nodes, but that requires understanding 
X3DOM code, which not every class of users wants or has time to do; In 
my opinion, X3DOM should match the capability provided by X3D in 
defining complex modelling class/object using X3D/javascript code/syntax
 <span style="text-decoration: underline;">only</span>. </span></span><span
 style="font-family: Calibri;"><br><br>That said, I am open to 
additional suggestion, discussion or links to more information! <br><br>Regards,
 Daniel<br><br><br><br><br><br></span><br><blockquote style="border: 0px
 none;" cite="mid:003801cfe260$00d09080$0271b180$@spawar.navy.mil" 
type="cite"><div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
 style="display:table;width:100%;border-top:1px solid 
#EDEEF0;padding-top:5px">          <div 
style="display:table-cell;white-space:nowrap;vertical-align:middle;width:100%">
        <a moz-do-not-send="true" href="mailto:richards@spawar.navy.mil" 
style="color:#737F92 
!important;padding-right:6px;font-weight:bold;text-decoration:none 
!important;">John Richardson</a></div>   <div 
style="display:table-cell;white-space:nowrap;vertical-align:middle;">   
  <font color="#9FA2A5"><span style="padding-left:6px">07 October 2014 
19:53</span></font></div></div></div><div 
style="color:#888888;margin-left:24px;margin-right:24px;" 
__pbrmquotes="true" class="__pbConvBody"><div>Hello,<br><br>Is this a 
loss of usability from the development perspective?<br><br>John F. 
Richardson<br><br>-----Original Message-----<br>From: X3D-Public 
[<a class="moz-txt-link-freetext" href="mailto:x3d-public-bounces@web3d.org">mailto:x3d-public-bounces@web3d.org</a>] On Behalf Of Andreas Plesch<br>Sent:
 Tuesday, October 07, 2014 7:03 AM<br>To: Daniel Vera<br>Cc: 
<a class="moz-txt-link-abbreviated" href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a><br>Subject: Re: [X3D-Public] Prototype<br><br>Hi 
Daniel,<br><br>there is the vague hint on 
<a class="moz-txt-link-freetext" href="http://www.x3dom.org/?page_id=158">http://www.x3dom.org/?page_id=158</a> to use DOM/HTML techniques, and there 
is a discussion on the x3dom developer mailing list suggesting to use 
the component system:<br><br><a class="moz-txt-link-freetext" href="http://sourceforge.net/p/x3dom/mailman/message/30219569/">http://sourceforge.net/p/x3dom/mailman/message/30219569/</a><br><br><a class="moz-txt-link-freetext" href="https://x3dom.readthedocs.org/en/latest/components/index.html#extending-x3dom">https://x3dom.readthedocs.org/en/latest/components/index.html#extending-x3dom</a><br><br>This
 talks about to how to define your own nodes, essentially in parallel to
 how x3dom.js defines nodes. Unfortunately, the example is a bit too 
basic and one would need to look at x3dom source to understand better 
how to do that. See for example 
<a class="moz-txt-link-freetext" href="https://github.com/x3dom/x3dom/blob/master/src/nodes/Geometry3D/Box.js">https://github.com/x3dom/x3dom/blob/master/src/nodes/Geometry3D/Box.js</a> .<br><br>Another
 basic idea is to create and manipulate nodes procedurally, not 
declaratively. The scene API helps with that:<br><a class="moz-txt-link-freetext" href="http://doc.x3dom.org/author/index.html">http://doc.x3dom.org/author/index.html</a>.
 So one could image a javascript function which inserts a series of 
nodes into the DOM based on provided parameters. This approach may be 
more accessible and there some basic examples on 
<a class="moz-txt-link-freetext" href="http://examples.x3dom.org/simpleExamples.html">http://examples.x3dom.org/simpleExamples.html</a> which provide pointers in 
that direction.<br><br>Hope this helps,<br><br>Andreas<br><br><br><br></div><div><!----><br><br>--<br>Andreas
 Plesch<br>39 Barbara Rd.<br>Waltham, MA 02453<br><br><br>_______________________________________________<br>X3D-Public
 mailing list<br><a class="moz-txt-link-abbreviated" href="mailto:X3D-Public@web3d.org">X3D-Public@web3d.org</a><br><a class="moz-txt-link-freetext" href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><br></div></div><div
 style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div 
style="display:table;width:100%;border-top:1px solid 
#EDEEF0;padding-top:5px">          <div 
style="display:table-cell;white-space:nowrap;vertical-align:middle;width:100%">
        <a moz-do-not-send="true" href="mailto:andreasplesch@gmail.com" 
style="color:#737F92 
!important;padding-right:6px;font-weight:bold;text-decoration:none 
!important;">Andreas Plesch</a></div>   <div 
style="display:table-cell;white-space:nowrap;vertical-align:middle;">   
  <font color="#9FA2A5"><span style="padding-left:6px">07 October 2014 
15:03</span></font></div></div></div><div 
style="color:#888888;margin-left:24px;margin-right:24px;" 
__pbrmquotes="true" class="__pbConvBody"><meta content="text/html; 
charset=ISO-8859-1" http-equiv="Content-Type"><div dir="ltr"><div><div><div>Hi
 Daniel,<br><br></div>there is the vague hint on <span class="im"> <a 
moz-do-not-send="true" target="_blank" 
href="http://www.x3dom.org/?page_id=158">http://www.x3dom.org/?page_id=158</a>
 to use DOM/HTML techniques, and there is a discussion on the x3dom 
developer mailing list suggesting to use the component system:<br><br><a
 moz-do-not-send="true" 
href="http://sourceforge.net/p/x3dom/mailman/message/30219569/">http://sourceforge.net/p/x3dom/mailman/message/30219569/</a><br><br><a
 moz-do-not-send="true" 
href="https://x3dom.readthedocs.org/en/latest/components/index.html#extending-x3dom">https://x3dom.readthedocs.org/en/latest/components/index.html#extending-x3dom</a><br><br></span></div><div><span
 class="im">This talks about to how to define your own nodes, 
essentially in parallel to how x3dom.js defines nodes. Unfortunately, 
the example is a bit too basic and one would need to look at x3dom 
source to understand better how to do that. See for example <a 
moz-do-not-send="true" 
href="https://github.com/x3dom/x3dom/blob/master/src/nodes/Geometry3D/Box.js">https://github.com/x3dom/x3dom/blob/master/src/nodes/Geometry3D/Box.js</a>
 .<br></span></div><div><span class="im"><br></span></div><span 
class="im">Another basic idea is to create and manipulate nodes 
procedurally, not declaratively. The scene API helps with that: <a 
moz-do-not-send="true" href="http://doc.x3dom.org/author/index.html">http://doc.x3dom.org/author/index.html</a>.
 So one could image a javascript function which inserts a series of 
nodes into the DOM based on provided parameters. This approach may be 
more accessible and there some basic examples on <a 
moz-do-not-send="true" 
href="http://examples.x3dom.org/simpleExamples.html">http://examples.x3dom.org/simpleExamples.html</a>
 which provide pointers in that direction.<br><br></span></div><div><span
 class="im">Hope this helps,<br><br>Andreas<br><br><br></span></div><span
 class="im"></span></div><div class="gmail_extra"><br><br><br 
clear="all"><br>-- <br>Andreas Plesch<br>39 Barbara Rd.<br>Waltham, MA 
02453
</div>

</div><div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div 
style="display:table;width:100%;border-top:1px solid 
#EDEEF0;padding-top:5px">          <div 
style="display:table-cell;white-space:nowrap;vertical-align:middle;width:100%">
        <a moz-do-not-send="true" href="mailto:d.a.vera@warwick.ac.uk" 
style="color:#737F92 
!important;padding-right:6px;font-weight:bold;text-decoration:none 
!important;">Daniel Vera</a></div>   <div 
style="display:table-cell;white-space:nowrap;vertical-align:middle;">   
  <font color="#9FA2A5"><span style="padding-left:6px">07 October 2014 
08:42</span></font></div></div></div><div 
style="color:#888888;margin-left:24px;margin-right:24px;" 
__pbrmquotes="true" class="__pbConvBody">
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
<div style="font-size: 
12pt;font-family: Calibri;"><span style="font-family: Calibri;">Hi 
Andreas,</span><br><span style="font-family: Calibri;">Do
 you have anything specific in mind? Is there anything that can be used 
currently to achieve </span><span><span style="font-family: Calibri;">functionalities

 similar to </span></span><span style="font-family: Calibri;">PROTO/EXTERNPROTO

 in X3DOM? <br><br>Best regards, <br><br></span><span>--<br>
<div style="line-height:16px; margin:6px 0; padding:8px 8px 8px 8px; 
border-top:1px #aeb1a6 dotted; border-bottom:1px #aeb1a6 dotted; 
font-family: 'Lucida Sans', Lucida Grande, Verdana, Arial, Sans-Serif; 
font-size:11px; color:#555555;">

<p style="font-family: Helvetica, Arial, sans-serif; font-size: 11px; 
color: #424242; line-height: 14px;">
        <span class="txt" style="font-size: 13px;" id="name-input">Daniel Vera</span>
        <br><span class="txt" style="font-size: 13px;" id="name-input"></span></p></div> </span><br><span
 style="font-family: Calibri;"><br></span><br></div></div><div 
style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div 
style="display:table;width:100%;border-top:1px solid 
#EDEEF0;padding-top:5px">          <div 
style="display:table-cell;white-space:nowrap;vertical-align:middle;width:100%">
        <a moz-do-not-send="true" href="mailto:andreasplesch@gmail.com" 
style="color:#737F92 
!important;padding-right:6px;font-weight:bold;text-decoration:none 
!important;">Andreas Plesch</a></div>   <div 
style="display:table-cell;white-space:nowrap;vertical-align:middle;">   
  <font color="#9FA2A5"><span style="padding-left:6px">05 October 2014 
22:03</span></font></div></div></div><div 
style="color:#888888;margin-left:24px;margin-right:24px;" 
__pbrmquotes="true" class="__pbConvBody"><meta content="text/html; 
charset=ISO-8859-1" http-equiv="Content-Type"><p dir="ltr">Hi Joe,</p>
<p dir="ltr">x3dom does not support proto nodes, see <a 
moz-do-not-send="true" href="http://www.x3dom.org/?page_id=158">http://www.x3dom.org/?page_id=158</a></p>
<p dir="ltr">You could ask on the x3dom developer mailing list about 
plans but my impression is that this not a priority since there may be 
other ways to achieve similar functionality.</p>
<p dir="ltr">Andreas</p>


<div>_______________________________________________<br>X3D-Public 
mailing list<br><a class="moz-txt-link-abbreviated" href="mailto:X3D-Public@web3d.org">X3D-Public@web3d.org</a><br><a class="moz-txt-link-freetext" href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><br></div></div></blockquote></div></body></html>