[far-future / robot UI] PolyCSS for 3D robot status and control interface #47

New issue

Open

opened 2026-06-03 20:17:10 -07:00 by pyr0ball · 0 comments

pyr0ball commented

2026-06-03 20:17:10 -07:00

Owner

Summary

PolyCSS (https://github.com/LayoutitStudio/polycss, MIT) — CSS-native 3D engine with per-face DOM events and transform gizmos — is well-suited for a robot status and command UI.

Why for robot control

Per-face DOM events: click a joint, a wheel, or a sensor face to command or inspect it
Transform gizmos: built-in manipulation handles for commanding robot positions
First-person nav mode: potential robot camera POV mode
Theme-aware: CSS-native rendering adapts to CF's theme system automatically

Performance scope

DOM rendering caps at ~10k polygons. This is fine for a command/status UI (slow interaction, not real-time kinematics). If the robot UI ever needs real-time 30Hz joint streaming, the same glTF assets port directly to Three.js — PolyCSS is a good starting point that doesn't lock in the asset format.

Relevant products

Home assistant robot (Labrador-equivalent concept, roadmap)
Raven robot control interface (far future)
cf-orch cluster visualization (topology of coordinator/agent/GPU nodes as 3D graph)

References

https://github.com/LayoutitStudio/polycss
License: MIT, 586 stars
Also see: website PolyCSS hardware renders ticket

## Summary PolyCSS (https://github.com/LayoutitStudio/polycss, MIT) — CSS-native 3D engine with per-face DOM events and transform gizmos — is well-suited for a robot status and command UI. ## Why for robot control - **Per-face DOM events:** click a joint, a wheel, or a sensor face to command or inspect it - **Transform gizmos:** built-in manipulation handles for commanding robot positions - **First-person nav mode:** potential robot camera POV mode - **Theme-aware:** CSS-native rendering adapts to CF's theme system automatically ## Performance scope DOM rendering caps at ~10k polygons. This is fine for a command/status UI (slow interaction, not real-time kinematics). If the robot UI ever needs real-time 30Hz joint streaming, the same glTF assets port directly to Three.js — PolyCSS is a good starting point that doesn't lock in the asset format. ## Relevant products - Home assistant robot (Labrador-equivalent concept, roadmap) - Raven robot control interface (far future) - cf-orch cluster visualization (topology of coordinator/agent/GPU nodes as 3D graph) ## References - https://github.com/LayoutitStudio/polycss - License: MIT, 586 stars - Also see: website PolyCSS hardware renders ticket