<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Andreas,<br>
<br>
This looks very interesting. I will need to spend some time on it
to make sure I fully understand it. <br>
<br>
I too struggled with understanding "style" in 3D. There is a style
to films (and the CG in it) that might be used. I think another
way to think of things is as like DEF/USE. The <class3d>
tags define the DEF and they are used in class3d='...'. I have not
tried to think through all of the potential DEF/USE cases to see
what does and does not work. So far I do know that it should work
for all Appearance related properties (Material, ImageTexture,
etc.). XSeen does not support modeling (models are imported), so
geometry constructions are not relevant. Animation is the other
big area. I don't know about that one yet. I am working on
revising the simple animation capability and will find out later.<br>
<br>
Leonard Daly<br>
<br>
<br>
<br>
<br>
</div>
<blockquote type="cite"
cite="mid:CAKdk67trp-Wf+eknGiJtuGW4Y4mvkbnNvc5Jjthqk-KkjNj7gQ@mail.gmail.com">
<div dir="auto">
<div dir="auto">In Leonard's nomenclature classes are
collections of specific styles. This is in contrast to HTML
where classes are collections of elements. Nevertheless, here
is a potential way to use paths or any css selector to assign
styles to matching elements in a preprocessing phase. Say
there is a tag such as </div>
<div dir="auto"><br>
</div>
<css3d objects=selectorString styles='shape box' />
<div dir="auto"><br>
</div>
<div dir="auto">where shape and box are defined class3ds.</div>
<div dir="auto"><br>
</div>
<div dir="auto">Then in a preprocessing step it would be
possible to go through all css3d elements, select matching
target elements and add a class3d='shape box' attribute to
each. In pseudocode:</div>
<div dir="auto"><br>
</div>
<div dir="auto">document.querySelectorAll('css3d').for
each(function(El){</div>
<div dir="auto">styles=El.styles</div>
<div dir="auto"><br>
</div>
<div dir="auto">document.querySelectorAll(sele<wbr>ctorString).for
each(addclass3d.bind(styles))</div>
<div dir="auto"><br>
</div>
<div dir="auto">)})</div>
<div dir="auto"><br>
</div>
<div dir="auto">function addclass3d(El) {</div>
<div dir="auto">El.setAttribute('class3d', this)</div>
<div dir="auto">\\better merge into existing value</div>
<div dir="auto">}</div>
<div dir="auto"><br>
</div>
<div dir="auto">This is rough but could work I think.</div>
<div dir="auto"><br>
</div>
<div dir="auto">The larger question if it is possible to
separate semantic content from presentation in 3d scenes. Is
geometry always content and size or color always style ? Are
small animations always just a stylistic aid, never critical ?</div>
<div dir="auto"><br>
</div>
<div dir="auto">In HTML CSS is mostly used to make pages
'pretty' and sometimes look coherent across a larger site.
What is the equivalent use for 3d scenes ? Perhaps this
suggests that css would be most useful if it worked across
multiple scenes ?</div>
<div dir="auto"><br>
</div>
<div dir="auto">Andreas</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<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>
</blockquote>
<p><br>
</p>
<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>
LA ACM SIGGRAPH Chair<br>
President, Daly Realism - <i>Creating the Future</i>
</font></div>
</body>
</html>