<html><head>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
</head><body 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;"
cite="mid:A145E877-D13C-4C08-909F-573776387E4F@igd.fraunhofer.de"
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:johannes.behr@igd.fraunhofer.de" style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">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
style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody"><blockquote type="cite"><pre wrap="">Don't x3dom components solve the proto problem? I've used them and they seem a lot less obtuse than protos
</pre></blockquote><pre wrap=""><!---->
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 wrap="">Sent from my iPhone
On 2015-02-14, at 15:08, David Sankel <a class="moz-txt-link-rfc2396E" href="mailto:camior@gmail.com"><camior@gmail.com></a> wrote:
</pre><blockquote type="cite"><pre wrap="">On Sat, Feb 14, 2015 at 9:51 AM, Alan Hudson <a class="moz-txt-link-rfc2396E" href="mailto:alan@shapeways.com"><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 class="moz-txt-link-freetext" href="http://goparallel.sourceforge.net/">http://goparallel.sourceforge.net/</a>
_______________________________________________
x3dom-developers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:x3dom-developers@lists.sourceforge.net">x3dom-developers@lists.sourceforge.net</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/x3dom-developers">https://lists.sourceforge.net/lists/listinfo/x3dom-developers</a>
</pre></blockquote><pre wrap="">------------------------------------------------------------------------------
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 class="moz-txt-link-freetext" href="http://goparallel.sourceforge.net/_______________________________________________">http://goparallel.sourceforge.net/_______________________________________________</a>
x3dom-developers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:x3dom-developers@lists.sourceforge.net">x3dom-developers@lists.sourceforge.net</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/x3dom-developers">https://lists.sourceforge.net/lists/listinfo/x3dom-developers</a>
</pre></blockquote><pre wrap=""><!---->
_______________________________________________
x3d-public mailing list
<a class="moz-txt-link-abbreviated" href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a>
<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>
</pre></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:alan@shapeways.com"
style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">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;"
__pbrmquotes="true" class="__pbConvBody"><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>
<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><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">13 February 2015
20:54</span></font></div></div></div><div
style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody"><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>
<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>