Settings and activity
5 results found
-
3 votes
An error occurred while saving the comment -
2 votes
An error occurred while saving the comment
Tina Diaz
commented
Native axis controls for weight and width would make variable fonts useful beyond just reducing asset size, especially if creators can animate those values on a text layer.
-
2 votes
-
3 votes
An error occurred while saving the comment
Tina Diaz
commented
Configurable anchors and occlusion controls would help with varied real-world objects.
-
1 vote
An error occurred while saving the comment
Tina Diaz
commented
For the error translation layer, include the node name and graph path alongside the underlying compiler message. With Graph YAML available, a source location or node identifier would make errors much easier to trace in version-controlled projects, even if the compiler text itself can’t be simplified.
A separate IDE may be a bigger maintenance burden than a Spectacles mode inside Lens Studio. A device-target selector could hide unsupported components, filter API docs and surface compatibility warnings in the editor, while keeping shared project workflows intact. Pairing that with native surface placement would address the main friction without splitting the toolchain or requiring developers to learn a second IDE.