3 ms·

Good work. I can envision live editing to become standard and we're bound to see new 'code' builders where programs can be expressed using graphics mixed with t

Good work. I can envision live editing to become standard and we're bound to see new 'code' builders where programs can be expressed using graphics mixed with text. That being said, editing text in 3D isn't fun. Text is by definition 2D and it's weird to edit it projected (although the idea itself seems cool). I'd be perfectly happy with a split screen of 2D editor + 3D scene being edited.

moron4hire 11y ago
It's necessary with the WebVR setting, though, because mixing traditional 2D elements with the VR scene is extremely jarring. I built Primrose specifically because, at the time, other VR live-programming demos were overlaying HTML elements with using CSS3 transform matrices to fake a 3D, barrel-distorted projection, which meant that there were two completely different Z-buffers (the WebGL one and the DOM one) and they didn't interact. Certainly this is not the most ideal setup, but I think it's a good baseline to continue to build from. I'm working on a game of collaborative AI bots that the user will program using a simple, not-JavaScript programming language. (maybe CoffeeScript, IDK, I actually slapped together a BASIC interpreter not too long ago for another demo I made). I think it will work better to organize functions 1-to-1 with editor objects, tied directly to the physical objects of which you're editing. I'm approaching it from a "crack open the back of the robot and twiddle the parameters" metaphor. I'm hoping the more concrete scenario will obviate some of those awkward issues you've mentioned.