minimize core interactions and their visualization by staying coherent #55

Open
opened 2 years ago by utopiah · 0 comments
Owner

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.
utopiah added the
demo
core interactions
documentation
labels 2 years ago
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: utopiah/text-code-xr-engine#55
Loading…
There is no content yet.