So you’re a web developer, and you’ve been hearing things about VR. I’m also a web developer, and I’ve also been hearing things about VR! And I’ve been blogging about it. Not just VR – but how VR is very likely to soon become both a crisis and an opportunity for web developers. So what are the prospects for VR for web developers?
Today is April 8, 2016. The Oculus Rift and the HTC Vive both tried to start shipping in the last couple of weeks – and it’s been a bit of a mess. But even so, eager early adopters have raved up and down that this revolutionary technology finally actually works.
As a sequel to my Feb 23 post X3DOM vs. Three.js, I’d like to quickly compare Blend4web vs. Three.js, using that same old arbitrary VRML file as a neutral sample. Blend4web is an add-on for Blender, the open-source 3D authoring tool I use.
Here’s how the Blender workspace containing my old VRML file looks when I export it using Blend4web:
And here’s the same Blender workspace exported as a COLLADA file and then imported into Three.js:
You can drag your mouse on either of those to move them around. Each button gives you a different motion when you drag. Each example uses each button in a different way.
Whether websites work in laptops but not phones – or whether VR works with goggles but not without – the solution then and the solution now, is to make web content that responds to whatever the heck hardware is being used to experience it.
Boris Smus is a man who understands the motivation behind “reponsive” web content, and responsive VR. From smus.com:
I remember the moment the so-called Browser Wars redefined everything we were doing on the web. It was the Twentieth Century. The web, and browsers, were the most amazing things ever. We didn’t give a darn about “open standards”, and we were creating these awesome Java Applets that could connect to a server, and provide multi-user interaction on the web. Then one day, one of my co-workers came into my office, looking like he’d just been hit by a bus.
“Microsoft has just released its new Java.” he told me.
“Cool.” I said, chewing my bubblegum and turning my attention back to the emacs window on my computer.
Here’s a quick look at X3DOM vs. three.js. Two very different tools, that both do something I’m very interested in – allow you to publish 3D content and virtual worlds on the open web, without a plugin.
I found two good ways to get 3D content (from an ancient VRML file) out of Blender, and out on the open web where anyone with a browser can see them without a plugin. So I’d like to compare X3DOM vs. Three.js.
You can drag your mouse on either of those to move them around. Each button gives you a different motion when you drag. Each example uses each button in a different way.Continue reading “X3DOM vs. Three.js”
My previous post was an introduction to X3DOM – which included a brief definition of the two components, X3D and DOM. I’d like to do another post, where I dig a little deeper into each of those. Continue reading “X3D and DOM”