6db929fe42
A map's phone legend (LegendMobile) announces its sheet with the composed 'dxmaps:legend-sheet' event, dispatched from the sheet element. The layout measures that element itself and lifts the circle to 8px above the sheet's top edge: collapsed or open, wherever the map ends (Simple Research's map stops 102px above the viewport, with its grid below), so the two never overlap. It re-measures on each event, on the sheet's own resize (a ResizeObserver, so the box is read after layout), on the pane's scroll and on window resize, coalesced to a frame with a 100ms backup for a page that gets no frames. Only a sheet on screen counts: another tab's pane (hidden or inert), a scrolled-away map, or state 'gone' leave the circle where it is today. With no event at all the placement is unchanged. --map-fab-clearance rises with the circle, and --map-fab-sheet-inset:0 is published only while a sheet lifts it, so that sheet can take the full width. The circle moves by transform (no layout property). Both CSS copies change identically. Measured with a stand-in sheet planted in a plugin's shadow root (it announces after its box is laid out, as the real sheet does), at 390 in en and ar, twice each: collapsed, open, after a scroll, another tab's sheet ignored, gone back to today. All pass. |
||
|---|---|---|
| .. | ||
| api | ||
| charts | ||
| colors | ||
| components | ||
| composables | ||
| constants | ||
| dashboards | ||
| data | ||
| elements | ||
| i18n | ||
| layouts | ||
| lists | ||
| maps | ||
| packet | ||
| packets | ||
| scripts | ||
| stores | ||
| styles | ||
| utils | ||
| vendor/cldr | ||
| index.js | ||
| ProfileLoader.vue | ||
| README.md | ||
library/ (@map) — the shared map template
The other half of the architecture (see ../plugin-designs/README.md):
every map in plugin-designs/<your-map>/ composes the reusable, parameterized pieces that live here.
Fix something here and every map benefits on the next build; break something here and every map
breaks — read components/WARNING.md before touching shared pieces.
| Folder | What lives there |
|---|---|
ProfileLoader.vue |
The root of every bundle: parses profile-config, loads the profile, provides the stores + config |
components/ |
Shared UI — map, legends, controls, popup (PeopleGroupDetail), tables, charts, hints (README) |
composables/ |
Shared logic — map engine (useMapInstance), provider switch, shadow-DOM styles, theming |
stores/ |
Per-instance Pinia stores (ui / map / data) — provided by ProfileLoader, injected by children |
api/ |
Data-source registry (sources.json) + fetch layer — the JAMstack runtime wiring |
colors/ |
Color sets maps opt into via profile-config.colorSet |
i18n/ |
The shared string catalogs (all maps speak the same languages) |
data/ |
Small shared datasets baked at build time (big served data lives in ../data/) |
constants/ |
Shared constants |
scripts/ |
Maintainer pipelines (posters, research) — not part of any bundle |
The rule of thumb (same as WARNING.md): custom code in your app-profile, reusable code here — and things only move from the first to the second once they've earned it.