Riffing on that last post about Node/Chrome compatibility. I would so love to be able to bring a fully functioning browser into VR, with an eye to being able to run chrome in Kiosk mode or even a version of Electron to be able to run Code or something like that inside.
However, unless it's amazingly easy to do, it's way down in the list of priorities.
However, I have been thinking of doing something like frame-buffer mapping as part of the emissary functionality. I have my VT100 emulator, and there's a Unity VNC client somewhere (not sure how good it is), but ultimately it would be nice to have something like a X/RDP/Citrix functionality. Also I envision lots of retro emulators, where something like this could expose the screen, possibly with point-audio. Old school games have pretty low resolution, so not so hard. RDP now can connect to one application on the remote side.
I don't know how this works into a virtualization/containerization world. Certainly X works in a container. Don't know enough about windows containers, though perhaps Wine might work too.
VR Worlds is a concept for building, essentially, an VR/AR (XR) Operating system, which allows any number of worlds to operate together and run in modern scalable containerized servers. Anyone can field their own worlds and so make their own rules rather than some giant top down architecture.
Subscribe to:
Post Comments (Atom)
Random Thoughts, Some Progress
Lots of work at work, so not as much time for projects. Smattering of thoughts: Godot doesn't really seem ready for prime-time with c...
-
So, the original idea for the _payload directory in the Emissary was to allow the initial state of meshes and whatever other assets might be...
-
Interesting article on asymmetric cryptography... Don't Use RSA So, looks like I will be using Elliptic Curves with Curve 25519 . ...
-
So, I wasn't really thinking that the V8 environments in the browser would be truly compatible with node or chrome. That leads to issue...
No comments:
Post a Comment