<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">John,<br>
<br>
</div>
<blockquote
cite="mid:CAGC3UEnYf1WQVXoqzFtnH+SOP=4keJPm_FZK8_ua=EKacwM1nw@mail.gmail.com"
type="cite">
<p dir="ltr">I think the real question is, do we need some kind of
Script node on the web? With fields and routes and everything
that comes with it. This is much harder to write than a Proto
Expander and much more useful. We can avoid Proto's with an
expander I'd say. I don't think scripts are in the way of
writing an expander (expander comes first), but I could be
wrong.</p>
</blockquote>
<br>
I do no object to a PROTO expander (MACRO). I think it could be
quite useful. It would allow the creation of potentially complex
objects with a simple node. Used carefully, it would allow the reuse
of some nodes (with DEF/USE) and allow a few nodes that need to
change from occurrence to occurrence. <br>
<br>
<blockquote
cite="mid:CAGC3UEnYf1WQVXoqzFtnH+SOP=4keJPm_FZK8_ua=EKacwM1nw@mail.gmail.com"
type="cite">
<p dir="ltr">We just need some effort to bring script nodes into
X3DOM. Can we use cobweb's?<br>
</p>
</blockquote>
<br>
I disagree with that for two reasons:<br>
<br>
1) HTML/X3DOM already has scripts in the form of standard
JavaScript. If you are bringing X3D into the DOM, then having two
different types of scripts would be really bad. One type is normal
HTML JavaScript, the other (X3D Script) requires definition of
fields, automatic calls (beginning and ending of frames); and change
to the event model.<br>
<br>
2) Cobweb does not run in the DOM. The entire set of X3D nodes is
removed from DOM consideration and completely handled separately. By
the time you figured out how to use Cobweb's script handling; your
are close to being integrated with the DOM.<br>
<br>
<br>
The fundamental question for X3D V4 is "<b><font color="#3333ff">will
it be integrated into the DOM?</font></b>"<br>
<br>
Once that is answered, then a whole lot of secondary questions are
resolved and only need development work, not design work.<br>
<br>
In case any has any doubts, my position is that <font
color="#3333ff"><b>X3D V4 MUST be DOM integrated</b></font>.<br>
<br>
<br>
Leonard Daly<br>
<br>
<br>
<br>
<blockquote
cite="mid:CAGC3UEnYf1WQVXoqzFtnH+SOP=4keJPm_FZK8_ua=EKacwM1nw@mail.gmail.com"
type="cite">
<p dir="ltr">
</p>
<div class="gmail_quote">On Feb 24, 2016 1:03 PM, "Leonard Daly"
<<a moz-do-not-send="true"
href="mailto:Leonard.Daly@realism.com">Leonard.Daly@realism.com</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> I asked this before but
I don't think I got any answers. This is a slight rephrase
of the question to help make it clearer.<br>
<br>
I am looking for examples of PROTOs (either internal or
external) that are<br>
1) non-trivial<br>
2) do not use one or more Script nodes<br>
<br>
<br>
By (1) I mean something that does something useful that is
not easy to do without using a PROTO. Something like the
Universal Media PROTOs (e.g., <a moz-do-not-send="true"
href="http://www.web3d.org/x3d/content/examples/Basic/UniversalMediaMaterials/_pages/page02.html"
target="_blank">http://www.web3d.org/x3d/content/examples/Basic/UniversalMediaMaterials/_pages/page02.html</a>)
provide a lot of convenience to the X3D developer, but each
one just defines a Material node with specific
characteristics.<br>
<br>
A PROTO that is used repeated in a scene providing a
critical feature might be an example of something that meets
(1).<br>
<br>
<br>
I am asking this to determine if it is necessary or useful
to have a PROTO expander (sort-of like a MACRO). The
expander would not support Script nodes. If there are no
examples to this question, then it indicates that PROTOs
need Script node(s). Either way, this has an impact on the
design of V4.<br>
<br>
<div>-- <br>
<font color="#333366"> <font size="+1"><b>Leonard Daly</b></font><br>
3D Systems & Cloud Consultant<br>
X3D Co-Chair on Sabbatical<br>
LA ACM SIGGRAPH Chair<br>
President, Daly Realism - <i>Creating the Future</i> </font></div>
</div>
<br>
_______________________________________________<br>
x3d-public mailing list<br>
<a moz-do-not-send="true" href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a><br>
<a moz-do-not-send="true"
href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org"
rel="noreferrer" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><br>
<br>
</blockquote>
</div>
</blockquote>
<br>
<br>
<div class="moz-signature">-- <br>
<font class="tahoma,arial,helvetica san serif" color="#333366">
<font size="+1"><b>Leonard Daly</b></font><br>
3D Systems & Cloud Consultant<br>
X3D Co-Chair on Sabbatical<br>
LA ACM SIGGRAPH Chair<br>
President, Daly Realism - <i>Creating the Future</i>
</font></div>
</body>
</html>