<div dir="ltr">Yep except because of browser element naming, you would need to say <Dave-SlidingDoor> or <MyPkg-SlidingDoor> i.e. it needs a prefix and a dash. Other than *that* I personally think that the future is, indeed, here.<br><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Feb 16, 2015 at 11:26 AM, 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">
    If we can use Web Components to make something custom, like this,
    then the future has finally arrived:<br>
    <br>
    <SlidingDoor axis='x' opendistance='.9' opensound='open.wav'
    closesound='close.wav' activation='bump' /><br>
    <br>
    Where 'SlidingDoor' is a 'smart object' consisting of some geometry,
    sensor(s), audio node(s), and perhaps even some scripts.<div><div class="h5"><br>
    <br>
    <br>
    <div>On 2/16/2015 10:37 AM, Tony Parisi
      wrote:<br>
    </div>
    <blockquote type="cite">
      <div dir="ltr">
        <div>
          <div>
            <div>
              <div>Actually, the entire point of a Web Component is to
                make it easy to instantiate custom nodes, for both
                programmers and non-programmers. Once a web component is
                implemented, the user simply instantiates it with a tag,
                just like any other DOM element.<br>
                <br>
              </div>
              Creating Web Components is a little harder than PROTOs,
              granted, but it's not too much harder. And creating PROTOs
              has *never* been easy for a novice/non-programmer. That's
              both because PROTOs and the Scripts that implement their
              innards have a lot of design quirks, but more so because
              of the historical interoperability issues between browser
              implementations.<br>
              <br>
            </div>
            IMO the PROTO ship sailed long ago. MNy $.02 is that if
            X3DOM is going to be relevant, it should stay away from
            PROTOs. Nothing but trouble there.<br>
          </div>
        </div>
        <div><br>
        </div>
        Tony<br>
        <br>
        <div><br>
        </div>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Mon, Feb 16, 2015 at 9:53 AM, Daniel
          Vera <span dir="ltr"><<a href="mailto:d.a.vera@warwick.ac.uk" target="_blank">d.a.vera@warwick.ac.uk</a>></span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div style="font-family:Calibri;font-size:12pt" bgcolor="#FFFFFF" text="#000000">
              <div style="font-size:12pt;font-family:Calibri"><span style="font-family:Calibri">Are there any (even
                  simple) practical examples on how to use webcomponent
                  to emulate proto in X3Dom? <br>
                  <br>
                  Also, was the purpose of PROTO in VRML to provide a
                  simple (i.e. VRML-syntax-only and accessible to non
                  programmer) way to define/instantiate custom nodes?
                  Having to use something like web component that
                  requires additional knowledge and programming, etc,
                  would miss the point in my opinion. Does it make
                  sense?<br>
                  <br>
                  Also, PROTO/EXTERNPROTOS mechanism is (with ECMA
                  script capabilities, the event model, etc.) the only
                  thing that differentiate VRML/X3D from "mere" 3D
                  interchange formats (I am thinking JT, 3DPDF etc,
                  which are increasingly used in my field of
                  application). Reducing X3Dom specification by not
                  implementing PROTO might contribute to mitigate this
                  differentiator and impact adoption for a certain class
                  of users? <br>
                  <br>
                  Regards, Daniel<br>
                  <br>
                  PS: apologies for sending this to multiple mailing
                  lists. plz let me know which one this should this be
                  mailed to.<br>
                  <br>
                </span>
                <blockquote style="border:0px none" type="cite">
                  <div style="margin:30px 25px 10px 25px">
                    <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 href="mailto:johannes.behr@igd.fraunhofer.de" style="color:#737f92!important;padding-right:6px;font-weight:bold;text-decoration:none!important" target="_blank">Behr, Johannes</a></div>
                      <div style="display:table-cell;white-space:nowrap;vertical-align:middle">
                        <font color="#9FA2A5"><span style="padding-left:6px">15 February 2015
                            17:41</span></font></div>
                    </div>
                  </div>
                  <div>
                    <div>
                      <div style="color:#888888;margin-left:24px;margin-right:24px">
                        <blockquote type="cite">
                          <pre>Don't x3dom components solve the proto problem? I've used them and they seem a lot less obtuse than protos
</pre>
                        </blockquote>
                        <pre>Partially. You can use x3dom components to provide e.g. a node-library but not to declare new node types as part of your content. This is what you can do with prototypes. 

Best regards
Johannes

</pre>
                        <blockquote type="cite">
                          <pre>Sent from my iPhone

On 2015-02-14, at 15:08, David Sankel <a href="mailto:camior@gmail.com" target="_blank"><camior@gmail.com></a> wrote:

</pre>
                          <blockquote type="cite">
                            <pre>On Sat, Feb 14, 2015 at 9:51 AM, Alan Hudson <a href="mailto:alan@shapeways.com" target="_blank"><alan@shapeways.com></a> wrote:
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.

Could you elaborate on specifically where the difficulties lie?

-- David Sankel 
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. <a href="http://goparallel.sourceforge.net/" target="_blank">http://goparallel.sourceforge.net/</a>
_______________________________________________
x3dom-developers mailing list
<a href="mailto:x3dom-developers@lists.sourceforge.net" target="_blank">x3dom-developers@lists.sourceforge.net</a>
<a href="https://lists.sourceforge.net/lists/listinfo/x3dom-developers" target="_blank">https://lists.sourceforge.net/lists/listinfo/x3dom-developers</a>
</pre>
                          </blockquote>
                          <pre>------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. <a href="http://goparallel.sourceforge.net/_______________________________________________" target="_blank">http://goparallel.sourceforge.net/_______________________________________________</a>
x3dom-developers mailing list
<a href="mailto:x3dom-developers@lists.sourceforge.net" target="_blank">x3dom-developers@lists.sourceforge.net</a>
<a href="https://lists.sourceforge.net/lists/listinfo/x3dom-developers" target="_blank">https://lists.sourceforge.net/lists/listinfo/x3dom-developers</a>
</pre>
                        </blockquote>
                        <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>
</pre>
                      </div>
                    </div>
                  </div>
                  <div style="margin:30px 25px 10px 25px">
                    <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 href="mailto:alan@shapeways.com" style="color:#737f92!important;padding-right:6px;font-weight:bold;text-decoration:none!important" target="_blank">Alan Hudson</a></div>
                      <div style="display:table-cell;white-space:nowrap;vertical-align:middle">
                        <font color="#9FA2A5"><span style="padding-left:6px">14 February 2015
                            16:51</span></font></div>
                    </div>
                  </div>
                  <div style="color:#888888;margin-left:24px;margin-right:24px"><span>
                      <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>
                        <br>
                      </div>
                    </span><span>
                      <div>_______________________________________________<br>
                        x3d-public mailing list<br>
                        <a href="mailto:x3d-public@web3d.org" target="_blank">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>
                      </div>
                    </span></div>
                  <div style="margin:30px 25px 10px 25px">
                    <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 href="mailto:andreasplesch@gmail.com" style="color:#737f92!important;padding-right:6px;font-weight:bold;text-decoration:none!important" target="_blank">Andreas Plesch</a></div>
                      <div style="display:table-cell;white-space:nowrap;vertical-align:middle">
                        <font color="#9FA2A5"><span style="padding-left:6px">13 February 2015
                            20:54</span></font></div>
                    </div>
                  </div>
                  <div style="color:#888888;margin-left:24px;margin-right:24px"><span>
                      <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>
                        </div>
                      </div>
                    </span><span>
                      <div>_______________________________________________<br>
                        x3d-public mailing list<br>
                        <a href="mailto:x3d-public@web3d.org" target="_blank">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>
                      </div>
                    </span></div>
                </blockquote>
              </div>
            </div>
            <br>
            _______________________________________________<br>
            x3d-public mailing list<br>
            <a href="mailto:x3d-public@web3d.org" target="_blank">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>
          <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                                   
                            <a href="tel:415.902.8002" value="+14159028002" target="_blank">415.902.8002</a><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>
      <br>
      <fieldset></fieldset>
      <br>
      <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>
</pre>
    </blockquote>
    <br>
    </div></div><span class="HOEnZb"><font color="#888888"><pre cols="72">-- 
Follow me! @thatvrguy</pre>
  </font></span></div>

</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>