Starry sky and the application viewer move into the Cesium adapter

src/sky/starrySky.js and src/app/viewer.js are Cesium through and
through, so they move into the adapter as src/render/cesium/starrySky.js
and applicationViewer.js; the ./application/viewer export points there.
The celestial ring's precise ICRF rotation reaches the shell through a
Cesium-free registry (src/sky/icrf.js) that the sky provides as it
loads; the application's renderer loads it, and so does
./render/cesium/unbound. Both files leave the Cesium allow-list.
This commit is contained in:
Sameh Khamis committed 2026-11-09 12:31:46 -08:00
1 parent a8a9cc73a4
commit e6d9ec0636
17 files changed
+110 -38

No files matched your search

+4 -2
View File
@@ -4,8 +4,9 @@
* layers a Cesium viewer with no renderer bound: the factories
* that build a camera, credits, effects, draw, frame, globe, input and query
* port over such a viewer when code first asks for one, a click's own
* Cesium picks (`rendererOf.js`), and the map engine the map stacks switch
* through (`src/maps/engine.js`).
* Cesium picks (`rendererOf.js`), the map engine the map stacks switch
* through (`src/maps/engine.js`), and the sky's precise ICRF rotation
* (`src/sky/icrf.js`).
*/
import './camera.js';
import './effects.js';
@@ -15,3 +16,4 @@ import './input.js';
import './mapEngine.js';
import './nativeClick.js';
import './query.js';
import './starrySky.js';