History

Doxa Maps 09adc903fc One shared print busy state, and the dashboard waits for its map before printing Driver test round 2, #2 — the half the @media print rules could not do. The complaint was "no loading indicator on a click": the reader presses Print, the dialog takes a moment to rise, and nothing says anything is happening. It is worse on this page than most, because what the dialog waits for is a MAP — press it a moment early and the sheet carries a grey rectangle. printInPlace.js gains printWhenReady({ waitFor, onBusy, timeoutMs }). This pattern already exists five times in the repo (upg-100-list `c54a11d5a`, four of exp's `786a83461`, PeopleGroupsWall.printWall); they agree on the easy half — set a flag, print, clear it — and each invents the hard half, which is what "ready" means and what happens when ready never comes. The hard half is the one that strands a reader, so it is the half that graduates: · THE TIMEOUT PRINTS. It does not reject and does not cancel. A reader who clicked Print and waited has asked for paper; a slow tile server is a reason to print a plainer map, not a reason to produce nothing. · allSettled, not all — one waiter that rejects must not cost the print. · onBusy clears in a finally, on every path: a rejected wait, a throwing print, a host with no window.print. A busy state that outlives its own operation makes the page look broken rather than slow. RegionCountryMap answers when it is done, and map.loaded() is not that answer — it reports true while tiles still stream, which is how gospel's charts printed blank twice today. The condition is: style applied, camera stopped, tiles for this camera in. It checks synchronously FIRST and only then subscribes to 'idle', because this component's own header already records that once('load') measured unreliable in both directions here — an event that fired before you listened never arrives. Always resolves, always removes its listener. The button is quiet, sits under the title, and is hidden on paper. Busy state carries aria-busy and :disabled, not just a changed label: the screen reader is told, and disabled is what actually stops a second print. Both strings are in all 11 locales; "Print" was already translated 23 times elsewhere in the tree under other keys, so this adds the key the dashboard's own catalogue lacked. Mutation-tested, since the failure this guards is the path nobody takes: a waiter that never settles returns "timeout" after the ceiling and prints anyway (201ms measured on a 200ms ceiling), a rejecting waiter still prints, and the busy flag returns to false in all three.		2026-09-28 20:35:40 +00:00
..
all-people-groups	Map errors in every language, and print buttons that show they are busy (UPG Neighbor, All People Groups, Prayer Walk Planner, Wall)	2026-09-28 18:34:16 +00:00
big-picture	min-height clamps height, so the pane could not hold the plugin it was pinning	2026-09-28 15:01:19 +00:00
cities-internet	Eleven plugin entries import the element helper they call	2026-09-28 17:40:35 +00:00
country-posters	Country Posters: a partner's basemap, night look, search switch and start view reach the map inside it	2026-09-28 18:40:21 +00:00
dashboard-plus-grid	A relative share link works when you click it, which is why nobody caught it	2026-09-28 17:40:34 +00:00
demo-map	Five plugins were silently monolingual, because the bootstrap was copied sixteen times	2026-09-28 17:40:34 +00:00
doxa-maps-spa	Phones: production maps not built for them stay closed and say why; experimental ones open with a notice	2026-09-28 17:53:38 +00:00
doxa-research-map	The legend held a slot for a toolbar this profile never draws	2026-09-28 17:53:39 +00:00
doxa-simple-map	Five plugins were silently monolingual, because the bootstrap was copied sixteen times	2026-09-28 17:40:34 +00:00
doxa-vision-card	Doxa Vision Card: take the page language from profile-config lang as well as locale	2026-09-26 01:10:51 +00:00
golden-path-check	golden-path-check: walk the develop-a-plugin-and-see-it-live path end to end	2026-09-22 03:55:18 +00:00
gospel-internet	Call the layer setup unconditionally, and stop the figure being crushed	2026-09-28 20:24:29 +00:00
gospel-resources	Seat the legend caret in the title bar, and let the target keep a narrow screen	2026-09-28 19:13:38 +00:00
key-cities	Eleven plugin entries import the element helper they call	2026-09-28 17:40:35 +00:00
my-upg-100-list	Put the UPG 100 choice on the surface that actually shows it	2026-09-28 19:41:29 +00:00
people-groups-grid	Regions batch: perRow boot, control inset, stats grid, print, two leaks, smaller watermark	2026-09-28 20:20:50 +00:00
plugin-studio	library: one embedScript for the app shells, replacing four private copies	2026-09-28 07:07:33 +00:00
pplr-data-maps	Eleven plugin entries import the element helper they call	2026-09-28 17:40:35 +00:00
prayer-walk-planner	Map errors in every language, and print buttons that show they are busy (UPG Neighbor, All People Groups, Prayer Walk Planner, Wall)	2026-09-28 18:34:16 +00:00
regions-dashboard	One shared print busy state, and the dashboard waits for its map before printing	2026-09-28 20:35:40 +00:00
research-dashboard	Five plugins were silently monolingual, because the bootstrap was copied sixteen times	2026-09-28 17:40:34 +00:00
research-map-plus-grid	A relative share link works when you click it, which is why nobody caught it	2026-09-28 17:40:34 +00:00
rudder-voice	Rudder: plain streaming by default; sentence detection only while the robot voice is on	2026-09-28 17:27:13 +00:00
stack-demo	Decouple prose: no go-base / nuxtbase / nuxtinator / doxa-base names in plugin comments and docs	2026-09-26 17:28:45 +00:00
template-bundle	Five plugins were silently monolingual, because the bootstrap was copied sixteen times	2026-09-28 17:40:34 +00:00
upg-neighbor	Map errors in every language, and print buttons that show they are busy (UPG Neighbor, All People Groups, Prayer Walk Planner, Wall)	2026-09-28 18:34:16 +00:00
wall-of-people-groups	Wall of People Groups: comment times and the unnamed-group fallback in the reader's language	2026-09-28 18:52:57 +00:00
.gitkeep	Rename app-profiles -> plugin-designs; build green under new naming (load-bearing paths updated, guards pass)	2026-09-17 18:18:18 +00:00
README.md	plugin-designs/README: the tree is dx-maps, and a bundle's tag is its folder name	2026-09-26 01:19:53 +00:00

README.md

plugin-designs/ — where YOUR maps live

The shared template lives in ../library/ (aliased @map) — you never edit it per-map. You build your map by making a folder here, plugin-designs/<your-map>/, and composing the template's building blocks. Your folder is yours (colors, API, i18n); the template is shared (Apache-2.0, propagated to every map on the next build).

Shared vs. yours — the balance

  library/  (@map)  ── SHARED, reusable, parameterized ──►  legend · map · map-controls
        │                                                    (every map reuses these)
        │  imported by
        ▼
  plugin-designs/<your-map>/  ── YOURS ──►  the map's "main" class (the .vue profile = the Vue
        │                                  instance for that map)
        └── src/            ── YOURS ──►  this map's OWN non-reusable components, colors, API, utils

  One bundle can hold as many maps as you want — add another .vue profile and rebuild.

Reusable → library/. The legend, the map, the map-controls are shared, parameterized components every map reuses. Fix once, every map benefits. Never edit it to customize one map.
This map's own → plugin-designs/<your-map>/. It holds two things: the map's "main" class (each .vue profile is the Vue instance for that map) and that map's own non-reusable components (in src/). Nothing here leaks to another map.
Many maps per bundle. The bundler bundles one map or many — add another flat .vue and rebuild.

Production or experimental — every profile declares itself

Every app profile is one of two things, and experimental profiles are unlimited and encouraged — create as many as you need:

Experimental, not built: prefix the folder with _ — the build skips it; it just sits in code. Zero cost, zero risk.
Experimental, built: builds normally, but it belongs in the Experimental section of the power app's layout (nav section) — never embedded on partner surfaces.
Production: a real product — main sections of the power app + individually embeddable.

(The power app = the SPA layout that composes all profiles into one application.)

The pattern in one picture

plugin-designs/<your-map>/     ← one FOLDER = one BUNDLE, named after the folder
   ├── index.js               ← entry: registers the custom element, finds the profiles
   ├── overview.vue           ← one .vue = one PROFILE (flat in the folder — no profiles/ subfolder)
   └── detail.vue             ← another profile in the SAME bundle

     builds to ─────────────► public/dx-maps/<your-map>/<your-map>.js   (one file)

Folder name = bundle name. Folders starting with _ or . are skipped (handy for WIP).
Each .vue = one profile (one map screen). One bundle can hold many.
Pick the profile at embed time with the profile field — every profile shares one bundle:

<script src="/dx-maps/<your-map>/<your-map>.js"></script>
<your-map profile-config='{"profile":"overview","tk":"pk.eyJ..."}'></your-map>
<your-map profile-config='{"profile":"detail","tk":"pk.eyJ..."}'></your-map>

Add a map — three steps

# 1. create the folder + one profile
mkdir -p plugin-designs/<your-map>
#    index.js   ← copy doxa-simple-map/index.js, rename the tag
#    <name>.vue ← your screen, built from @map/* blocks (flat in the folder)

# 2. build
npm run build            # → public/dx-maps/<your-map>/<your-map>.js
#    (just this one:  BUNDLE=<your-map> npm run build:bundle)

# 3. embed the script tag + element (dev staging at `npm run dev` shows a paste-ready snippet)

Your three things (everything else is shared)

Colors — how pins are colored. Pick one the template ships (getColorStrategy('language-family')), or drop your own in plugin-designs/<your-map>/src/colors/ (start from template-bundle/src/colors/example-mode.js). Never edit @map/colors/ to recolor your map.
API — your map reads its data from the profile-config on the page, so the same bundle points at different data with no rebuild. DataSourceManager accepts csv (bundled file), api (one JSON URL), or rest-api (a live REST endpoint, the default). Prefer the real API over inlined JSON.
i18n — the template ships 11 base locales in @map/i18n/locales/. Use useI18n() for strings and RTL_LOCALES for right-to-left; add or override strings from your own profile.

The one hosting variable

The only thing that changes between hosting modes is the <script src>: a relative path when your own site serves the file, or an absolute CDN URL when a partner site serves it. The bundle is identical either way. See ../documentation/CONTRIBUTING.md for the two CDN modes and partner-site embedding.

Profile patterns (mix freely)

Individual — one .vue per bundle (simplest).
Parameterized — one profile, behavior driven by profile-config props (e.g. tabs[]).
Nested — one profile that renders others (workbench-style, like doxa-research-map).