[x3d-public] Inline > type field > for loading / converting / parsing other content

[GPU Group]

Inline > content type field > for loading / converting / parsing other
content
other file formats - .obj, .ply, .json - may contain content suitable for
converting into equivalent web3d nodes / scenegraphs. In theory this could
be done while loading the content as an inline based on file suffix. But
those generic file type suffixes don't say what type of nodes we are
expecting to get / want to extract or convert to web3d nodes.
Option 0: Sniffing the file for automatic detection of suitable web3d node
content
Option 1: A new node type, derived from Inline, for each combination of
file suffix and desired content conversion - assumes main scene author with
the Inline URL also knows the type of content / conversion
Option 2: an additional field on standard Inline, saying what content
converter to use, an enum field with things like "SPLAT", "CESIUM"
Then the web3d browser developer would write code to process / convert the
(file type, content converter type) cases to web3d nodes/scenegraph after
Inline loads the file.

-Doug
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20260325/a1bc2f10/attachment.html>