For example the wrist shortcut is a cube. It's visually interesting but because it is "just" a shortcut it would be more understandable to show the actual content of the shortcut, e.g switchToWireframe() and thus all following interactions, e.g activating (even though tapping is nice), removing, replacing, etc would follow.
Alternatively it could be the other way around, namely that each executable code snippet (i.e text preppended with jxr ) could have a 3D model attached to it. In that case the cube would be coherent.
For example the wrist shortcut is a cube. It's visually interesting but because it is "just" a shortcut it would be more understandable to show the actual content of the shortcut, e.g `switchToWireframe()` and thus all following interactions, e.g activating (even though tapping is nice), removing, replacing, etc would follow.
Alternatively it could be the other way around, namely that each executable code snippet (i.e text preppended with `jxr `) could have a 3D model attached to it. In that case the cube would be coherent.
For example the wrist shortcut is a cube. It's visually interesting but because it is "just" a shortcut it would be more understandable to show the actual content of the shortcut, e.g
switchToWireframe()
and thus all following interactions, e.g activating (even though tapping is nice), removing, replacing, etc would follow.Alternatively it could be the other way around, namely that each executable code snippet (i.e text preppended with
jxr
) could have a 3D model attached to it. In that case the cube would be coherent.