Draw the vessels layer's ships through the renderer's ports

The ships are one icon set from the draw port, held on course with hold
motion segments and drawn over depth as before; the layer keeps what it last
drew in an icon book and reads focus and pick ownership back from there,
matching clicks on the draw hit's set and id. Its frame hook, camera pose,
horizon test and screen projection come from the frame, camera and query
ports, with the horizon lift in geo/horizon judging the same point the GPU
cull does. The icons' draw set is disposed when the layer is destroyed.

rendering.js no longer imports Cesium or touches the scene's primitives,
picks, render events or camera, and leaves the Cesium allow-list. It still
reads the canvas size for the label budget. Callers of the vessels entry
load the Cesium adapter's unbound fallbacks.
This commit is contained in:
Sameh Khamis committed 2026-11-07 00:38:20 -08:00
1 parent bb85e0fa74
commit f6422d2247
16 files changed
+394 -190

No files matched your search

+4
View File
@@ -1109,6 +1109,10 @@ destroying the layer cancels pending work and ignores late results.
`./layers/vessels` package entry. The factory owns feed lifecycle, keyed records,
rendering, selection, trails and cards in separate components. The standalone
entry supplies its AISStream source, scene services and existing row limits.
Its ship icons are one renderer icon draw set (held motion, course rotation,
focus emphasis, horizon cull) and the entry no longer reaches Cesium, so a
caller handing it a Cesium viewer, with no renderer bound,
loads the `./render/cesium/unbound` export once first.
Incomplete observations retain missing keyed vessels for at most five minutes
since their last accepted receipt, within the renderer's row budget (plus the