<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 4/14/2017 11:53 AM, Michalis
Kamburelis wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAKzBGZP5=iS2s12ynTd-ErDN+hgg7Nj9-tWA8FS+gjPsp9w2_w@mail.gmail.com">
<pre wrap="">2017-04-14 17:54 GMT+02:00 Leonard Daly <a class="moz-txt-link-rfc2396E" href="mailto:Leonard.Daly@realism.com"><Leonard.Daly@realism.com></a>:
</pre>
<blockquote type="cite">
<pre wrap="">I just had an inspiration and would like to run it by people. This may have
been obvious to everyone else, but it's the first time I have thought of it
this way.
...
</pre>
</blockquote>
<pre wrap="">
In other words, every Shape also has additional fields "translation",
"rotation", "scale"... (It was easier in my head to express it like
this, but I think that this is equivalent to your idea?).</pre>
</blockquote>
<br>
Yes it is!<br>
<br>
<blockquote type="cite"
cite="mid:CAKzBGZP5=iS2s12ynTd-ErDN+hgg7Nj9-tWA8FS+gjPsp9w2_w@mail.gmail.com">
<pre wrap="">It's a handy shortcut in this case, and probably would be easy to
implement (after all, it's the same as Transform with 1 single child
Shape). But it has a price: we create a complicated node that has
capabilities of both Shape and Transform, instead of splitting this
functionality into 2 separate nodes (as we do now). So both
specification, and the implementation, do become a little more
complicated.</pre>
</blockquote>
<br>
It does have implementation issues, especially for the way X3D
people tend to think about things. The complexity occurs when you
want to change things in the structure. It also gets really messy if
you have a full-blown IndexFaceSet instead of a Cone.<br>
<br>
<blockquote type="cite"
cite="mid:CAKzBGZP5=iS2s12ynTd-ErDN+hgg7Nj9-tWA8FS+gjPsp9w2_w@mail.gmail.com">
<pre wrap="">But if it's important for interoperability with other important 3D
format, then I'm OK with it.</pre>
</blockquote>
<br>
I think existing X3D encodings would be (round-trip) convertable to
this format -- at least for a non-dynamic scene. Handling ROUTEs
would get complicated.<br>
<br>
-- <br>
<div class="moz-signature"><font class="tahoma,arial,helvetica san
serif" color="#333366">
<font size="+1"><b>Leonard Daly</b></font><br>
3D Systems & Cloud Consultant<br>
LA ACM SIGGRAPH Chair<br>
President, Daly Realism - <i>Creating the Future</i>
</font></div>
</body>
</html>