<div dir="ltr">People on this thread should really be thinking about Web Components for this. It's PROTOs done the DOM way. Redesign X3DOM as web components... that's what I am doing with GLAM as we speak (though it's not in the repo yet)<br><br>Tony<br><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 13, 2015 at 2:28 PM, Dave A <span dir="ltr"><<a href="mailto:dave@realmofconcepts.com" target="_blank">dave@realmofconcepts.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div bgcolor="#FFFFFF" text="#000000">
    I too was dismayed at the decision not to implement protos in x3dom.
    The argument is that the same functionality can be attained via
    javascript and DOM coding. Which is true. What we lose with that
    though is the modularity, that is to say, having a 'smart object'
    all in one file. As I see it, currently, there would be a .x3d file
    and a .js file to go with it.<br>
    <br>
    Perhaps if an x3d (x3dom) file can include both <x3d> section
    and <script> section, at least they can be packaged into the
    same file. I don't think that would be very hard to implement.<br>
    <br>
    Of course, the handling of interpreting protos (fields and binding
    them etc) would need to be coded. Not all 'smart objects' include
    VRML script nodes. Yeah, the more I think of it, it would be really
    handy to have protos implemented in x3dom per se, rather than
    externally coding all that. At least for field binding.<br>
    <br>
    Dave Arendash<div><div class="h5"><br>
    <br>
    <div>On 2/13/2015 12:54 PM, Andreas Plesch
      wrote:<br>
    </div>
    </div></div><blockquote type="cite"><div><div class="h5">
      <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<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>
                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"<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>
              </blockquote>
            </div>
          </div>
        </div>
      </div>
      <br>
      <fieldset></fieldset>
      <br>
      </div></div><pre>_______________________________________________
x3d-public mailing list
<a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a>
<a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><span class="HOEnZb"><font color="#888888">
</font></span></pre><span class="HOEnZb"><font color="#888888">
    </font></span></blockquote><span class="HOEnZb"><font color="#888888">
    <br>
    <pre cols="72">-- 
Follow me! @thatvrguy</pre>
  </font></span></div>


<br>_______________________________________________<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" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><br><br>Tony Parisi                             <a href="mailto:tparisi@gmail.com" target="_blank">tparisi@gmail.com</a><br></div><div>Founder, Third Eye                <a href="http://www.thirdeye.gl/" target="_blank">http://www.thirdeye.gl/</a><br></div>Follow me on Twitter!             <a href="http://twitter.com/auradeluxe" target="_blank">http://twitter.com/auradeluxe</a><br><div>Read my blog at                     <a href="http://www.tonyparisi.com/" target="_blank">http://www.tonyparisi.com/</a><br></div>Learn WebGL                         <a href="http://learningwebgl.com/" target="_blank">http://learningwebgl.com/</a><br><div><div>Mobile                                    415.902.8002<br></div><div>Skype                                     auradeluxe<br></div><br>Read my books! <i><br></i><i><i>Programming 3D Applications in HTML5 and WebGL<br><a href="http://www.amazon.com/Programming-Applications-HTML5-WebGL-Visualization/dp/1449362966" target="_blank">http://www.amazon.com/Programming-Applications-HTML5-WebGL-Visualization/dp/1449362966</a><br></i>WebGL, Up and Running</i><br>
<a href="http://www.amazon.com/dp/144932357X" target="_blank">http://www.amazon.com/dp/144932357X</a><br><br></div></div></div></div></div></div></div></div></div>
</div>