[x3d-public] url MFString handling

[GPU Group]

sadly freewrl goes down the list untill file found then stops,
regardless if the contents are the right type or parse.
DEF II Inline
{
   # will it get to cone.wrl? stops at (found) gif, displays black screen.
  url [ "../helpers/back.gif" "../cone.wrl" "../empty.wrl"
"../no_exist.wrl"]
}
gets to cone.wrl:
 url [ "../no_exist.wrl"  "../cone.wrl" "../empty.wrl" ]
stops at empty.wrl:
url [ "../empty.wrl"   "../cone.wrl" ]
empty.wrl:
#VRML V2.0 utf8
So it seems to be designed for when resources have moved relative to scene
file, for example
url["red.png" "helpers/red.png" "http://hostsite.com/scenery/helpers/red.png
"]
would save you from reworking your urls when you move from one site
-localhost- to a public server during scene development.
-Doug

On Tue, Apr 19, 2022 at 7:36 PM Andreas Plesch <andreasplesch at gmail.com>
wrote:

> x3dom currently lacks support for back-up urls to use if the first
> urls do not work. I am trying to add support and wonder how to deal
> with corner cases.
>
> The spirit of the spec. here is pretty clear:
>
> https://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/networking.html#X3DUrlObject
>
> says that a url which cannot be located or if the retrieved data
> cannot be interpreted should be skipped. Subsequent urls are then used
> as back-ups.
>
> Currently, x3dom checks if an inline x3d url can be parsed as xml and
> if so if it has a Scene element.
>
> The first corner case happens if there is a X3D element but it does
> not contain a Scene element. This could be interpreted to mean an
> empty X3D document with an empty Scene, or that it perhaps should be
> skipped as not interpretable. I would probably favor skipping as this
> would normally happen by mistake.
>
> The second corner case is a Scene element without content. Should such
> X3D be considered interpretable ?  I think x3dom is currently set up
> to parse it without error resulting in an empty Scene, probably with
> default NavigationInfo and Viewpoint. So this could be considered
> interpretable and not be skipped.
>
> https://www.web3d.org/x3d/content/examples/X3dSceneAuthoringHints.html#urls
>
> says a result needs to be "legal". But legal is by definition what is
> provided in the spec., eg. comes down to being interpretable.
>
> The tooltip at
> https://www.web3d.org/x3d/content/X3dTooltips.html#Inline.url
>
> does not seem to further clarify.
>
> Any feedback appreciated,
>
> Andreas
>
> --
> Andreas Plesch
> Waltham, MA 02453
>
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20220420/00fca2b0/attachment.html>