[x3d-public] IMPORT/EXPORT Use [was: Statement permitted placements]

[John Carlson]

No reason to choose xhtml over HTML.   What I would like however, is
separate animation of each flower.

John

On Jul 17, 2017 10:04 AM, "Leonard Daly" <Leonard.Daly at realism.com> wrote:

John,

Just like my tree/forest example, but prettier :-)

Then let's do flowers.xhtml with Inlines.   I don't mind.   I'm imagining
one inline to include everything else, and an inline file included multiple
times, one for each flower.


Any particular reason to use XHTML over HTML? Is it just for enforcement of
strictness?


This is exactly where DEF (or ID) value modification gets hard. Using X3DOM
terminology, I can have an inline for a flower. A plant has 5 flowers, so I
name them uniquely using namespacename='f1', ..., 'f5'. Now I have a garden
with 20 plants. I can name each plant uniquely (namespacename='p1',
...'p20'), but I still have 20 f1's, etc. namespacename would need to
propagate all of the way down the tree. Each flower would have a prefix
something like 'pN__fJ__'; 1<=N<=20, 1<=J<=5 to ensure uniqueness.

Value rewriting is a nice concept, but it's not just a simple solution. I
don't have a solution that I find really satisfying.



-- 
*Leonard Daly*
3D Systems & Cloud Consultant
LA ACM SIGGRAPH Chair
President, Daly Realism - *Creating the Future*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20170717/9f3cbc90/attachment.html>