mirror of
https://github.com/bilawalsidhu/gods-eye-view.git
synced 2026-11-16 16:22:20 +00:00
- src/app/layers/renderers.js: the layer renderer registry
(registerLayerRenderers(engineKind, { [layerId]: factory }),
rendererFor(layerId, engine), layerAvailableOn(layerId, engineKind)).
Every application layer is registered for Cesium as CESIUM_BUILTIN (it
still draws itself until its render/cesium.js); Navara factories come with
the layer tasks. On it, the stable availability API phase 4 injects into
its layer list: createLayerAvailability(engineKind) →
{ engine, isAvailable(id), available(), unavailable() } with { id, name }
rows (src/app/layers/directory.js holds the ids and names in catalog
order; a test keeps it equal to the constructed catalog).
- createApplicationCatalog({ engineKind, availability }) constructs only the
layers the engine can show, in the same order (shared instances made
once, on demand); the catalog carries `availability` and the others'
metadata (`unavailableMetadata`). Cesium builds the same 30 layers in the
same order as before; Navara builds none yet (no Navara renderers) - the
standalone app now asks the catalog for it instead of making an empty one.
- catalogControlServices: a role whose layer the engine leaves out gets an
empty stand-in (absentLayerControlServices folded in); any other missing
layer is still a wiring error.
- LayerLifecycle(viewer, { engine }): every module call (init, enable,
update, disable, destroy) gets { signal, engine } as its second argument;
viewer is null on Navara.
- Links: a link that turns on layers this engine leaves out keeps them in
the durable state (re-saved links carry them; back on Cesium they turn
on) and activates nothing; a notice names them ("NOT ON THIS ENGINE · Kept
in the link: …"). The Navara notice lists the engine's data layers from
the registry.
- The dev launcher's CCTV wiring check matches the new catalog form.
38 lines
1.3 KiB
JavaScript
38 lines
1.3 KiB
JavaScript
import { createSurfaceServices } from '../app/surfaceServices.js';
|
|
import { createApplicationRequestServices } from '../services/requests.js';
|
|
import { createApplicationCatalog } from '../app/constructCatalog.js';
|
|
import { createStandaloneLayerSources } from './layerSources.js';
|
|
export { createStandaloneReferenceSources } from './layerSources.js';
|
|
|
|
/** Create fresh layer instances using the existing standalone source choices. */
|
|
export function createStandaloneCatalog({
|
|
nepalBoundaryResolver,
|
|
engineKind = 'cesium',
|
|
sources = {},
|
|
streetLevelProviders,
|
|
signal = new AbortController().signal,
|
|
surface = createSurfaceServices({
|
|
terrainSource: createApplicationRequestServices().terrain,
|
|
signal,
|
|
}),
|
|
} = {}) {
|
|
return createApplicationCatalog({
|
|
engineKind,
|
|
nepalBoundaryResolver,
|
|
surface,
|
|
sources: createStandaloneLayerSources(sources),
|
|
streetLevelProviders,
|
|
signal,
|
|
vesselOptions: {
|
|
maxRows: import.meta.env?.VITE_AIS_LIVE_MAX_ROWS,
|
|
maxLabels: import.meta.env?.VITE_AIS_LIVE_LABEL_MAX_ROWS,
|
|
},
|
|
});
|
|
}
|
|
|
|
// Direct compatibility callers share one catalog; application startup supplies its own.
|
|
let compatibilityCatalog;
|
|
export function getStandaloneCatalog() {
|
|
return (compatibilityCatalog ||= createStandaloneCatalog());
|
|
}
|