[x3d-public] Most portable way to wrap X3D Player by App
yottzumm at gmail.com
Fri May 31 18:21:49 PDT 2019
Probably the best idea is to deploy the x3d file with the appropriate content type in apache, or override the content type header when you send back the x3d file to the web client. Then the web client should pick the appropriate X3D browser for that content type. It may require a bit more effort on the part of the user or X3D browser to set the X3D content type->X3D browser map entry.
I thought I’d toss that in. I have no real issues with .x3d files launching BS Contact, that I know of, without any scripts.
Sent from Mail for Windows 10
From: Christoph Valentin
Sent: Thursday, May 30, 2019 7:55 AM
Subject: [x3d-public] Most portable way to wrap X3D Player by App
Once I used Visual Basic to wrap BS Contact with my own little GUI application, which was quite easy given you had access to Contact SDK, but seems to be deprecated by Microsoft now.
Then I used HTML pages to wrap BS Contact, which seems to be deprecated by Mozilla et al now.
So, what is the most portable way to wrap an X3D Player (not only BS Contact) by some small GUI application of your own?
Or should I have "everything within the scene" and "never use external GUI", using X3D Players in standalone without any wrapper?
Or should I wait for X3D v4 to have no X3D Player at all, just W3C Browser, and do the wrapper in HTML/JS?
Any hint welcome. Time does not matter, but I need a "final" perfect solution. Do not want to change the things every two years.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the x3d-public