[x3d-public] Appearance of Geometry in HTML

[John Carlson]

I’m not even sure why Shape and IndexedFaceSets are required over HTML div and span + some form of CSS.  Something to think about.

Sent from Mail for Windows 10

From: Leonard Daly
Sent: Monday, August 14, 2017 11:21 AM
To: X3D Public
Subject: [x3d-public] Appearance of Geometry in HTML

If HTML/CSS world, the appearance of an element is (ideally) set in the appropriate style definitions for the element using a combinations of classes, ids, tags, and hierarchy. This includes it's edge effects (border style, corner rounding, padding) and internal appearance (color, background color, gradients, fonts, etc.). 
Using the same environment (HTML/CSS) and adding the 3D dimension (and maybe second cameras, markers, etc.) should the appearance of objects (geometry) be controlled by the appropriate style definitions? Why or why not?
If CSS+1D style definitions are used, then there is no need to any appearance nodes (Material, ImageTxture, etc.). It might be done as <Shape class='sign speedLimit'><IndexedFaceSet ...></Shape>. The classes would add the black border, yellow background, text color, etc.
The disadvantage is that some geometries may be require an extremely complex vertex (or face) assignment for this to be practical.
This method does align nicely with HTML and allows HTML tools and concepts to be carried over to 3D/VR/AR/xR.

-- 
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/20170814/6500ed73/attachment.html>