[x3d-public] Most portable way to wrap X3D Player by App

[GL]

I feel exactly the same way. Too many times I've tried relying on some company's offering in my own projects, only to have them change things out or cancel, thereby breaking my work. At this point, my goals are to build solutions that are as free of dependencies as can be. This means, I am not only gearing up to create a custom GUI, but I've also began the process of creating a 3D browser entirely optimized to the specific needs I wish to fulfill. This is one raison why I like X3D's open standards; code that I wrote 20 years ago remain valid today, and I trust that I can count on X3D for the next 20 years. 

 

In your case, I'd suggest building your own application with C++ instead of VB, thus allowing you better control of what you're doing. It's more work, but it's work much less likely to let you down in the long run. We did trust web browsers before, but look at where we are now. So I am personally quite reluctant in going that way again, with what seems to me now like a house of cards. Good as a temporary stepping stone to bring users in no doubt, but for a permanent fully-interactive 3D world, the previous approach is a no brainer. GL

 

________________________________________________________

* * * Interactive Multimedia - Internet Management * * *

  * *  Virtual Reality -- Application Programming  * *

    *   3D Net Productions  3dnetproductions.com   *

 

 

From: x3d-public [mailto:x3d-public-bounces at web3d.org] On Behalf Of Christoph Valentin
Sent: Thursday, May 30, 2019 8:55 AM
To: x3d-publicweb3d.org
Subject: [x3d-public] Most portable way to wrap X3D Player by App

 

Hi all,

 

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.

 

KR

Christoph

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20190531/937ea49a/attachment.html>