History

doxa-maps-88655c70 1d4fe185e3 Some checks are pending build-gate / build (push) Waiting to run Details Full table headers via horizontal scroll, and a full-screen table Driver, on the people-groups table under the map: "I would like to add a horizontal scroll bar so that instead of ABBREVIATING the headers, we can have the FULL headers in the table", and "I would also like to add a FULL SCREEN button to the table, so that if you want you can open up the table to be full screen." These ship together on purpose. The table now shows seven data rows by default because we are reclaiming vertical space; a deliberately small table is only an honest trade if the reader can get a big one on demand. The cap and its release are one change. HEADERS ARE NO LONGER ABBREVIATED. text-overflow:ellipsis is gone from .rd-th. Ellipsis destroys information with no way to recover it -- "Engageme..." is not a column name, and unlike a truncated VALUE it has no menu behind it. Horizontal scroll preserves it: the full text always exists and is always reachable. This is the same mechanism already applied to the chart legends (nowrap + overflow-x:auto), deliberately reused rather than a second invention. THE FLOOR IS MEASURED, NOT ESTIMATED. Columns are flex:<w> 1 0, which can never overflow -- flex-basis 0 plus shrink means every column collapses to whatever the container offers, so scrollWidth always equalled clientWidth and overflow-x had nothing to scroll. Each column now carries a min-width derived from its own header. A first pass guessed 7.1px/char, which put the summed floor at 675px against an 878px scrollport, so it never bound and no scrollbar could appear at any width. Measured live by cloning each header out of flex flow: worst case is 9.75px/char (Language 78px/8ch), so 9.9 covers every label, +12px reserves the sort indicator. Summed floor 742px + 30px checkbox. That floor sits BELOW the 1440px scrollport on purpose. At 1440 the eight columns genuinely fit and there is nothing to scroll; forcing a scrollbar there would invent a defect. It binds at 1280 and below, which is exactly where the truncation being complained about was happening. ROW WIDTH IS SHARED, NEVER INTRINSIC. An intermediate pass used width:max-content to create the overflow. It did -- and sized every row to ITS OWN content, so a row holding "Lao People's Democratic Republic" laid out wider than the row above it. That is not a table but a stack of independent flex lines: screenshot- verified ragged, with Country/Region/Language stepping left and right on consecutive rows while the header, correctly aligned, disagreed with all of them. The measurement said so too and was read past: scrollWidth was 969 at the top of the list and 1051 after scrolling, i.e. the table's width depended on which rows happened to be rendered. Head, rows and footer now share one explicit width (summed floor as min-width, width:100%), so nothing is intrinsic and the column grid holds at every scroll offset. The sticky header stays pinned on the vertical axis only, which is correct: it must travel sideways with the body or the labels detach from the columns they name. The footer is a SIBLING of the scrollport, so it is translated in lockstep from the scroll handler -- otherwise the population total slides out from under its own column. FULL SCREEN is CSS pseudo-fullscreen, not requestFullscreen(). The native API promotes the element to the browser's top layer, detaching it from the cascade this table is built on, and needs allow="fullscreen" to work in the iframe embed this dashboard actually ships in. Pinning the wrapper with position:fixed keeps the element where it is in the tree, so inherited tokens and ancestor rules keep applying and only the two rules we mean to override are overridden. Esc exits. The seven-row cap is released with max-height:none !important, and !important is the honest tool rather than a specificity war: the first attempt lost 0-2-0 to the shell's 0-3-0 selector and rendered a 900px box containing a 182px table -- the exact failure its own comment warned about. That shell rule is also being rewritten concurrently, so matching its selector would break on the next edit. library/components/map-controls/FullscreenButton.vue was read first and does not fit: it resolves its target as the SHADOW HOST, so pointed here it would fullscreen the whole dashboard rather than the table; it renders MapControlButton, a circular control built to float over a canvas; and it depends on vue-i18n, which this bundle does not use. Making it fit means adding a target prop and a chromeless variant to a component with seven map consumers to serve one non-map caller, so this stays local until a second table wants it. Verified at 1280 and 1440, real browser, live data: headers complete with text-overflow clip and no cell clipped; scrollWidth 867 vs clientWidth 718 with the last column's left edge moving 1045 -> 896; rows recycle (abai-sungai -> deaf-comorans) with the rendered count bounded at 14; zero ragged columns and zero head-vs-row drift at every scroll offset; fullscreen 244 -> 900px with the keyhole 182 -> 838 and 45 rows rendered, restoring exactly on exit. check:fits-screen 17/17.		2026-09-23 20:25:08 +00:00
..
all-people-groups	light the remaining unconditional loading overlays and the copy-me starter	2026-09-21 16:40:53 +00:00
big-picture	Stop Big Picture showing the same total twice	2026-09-23 15:32:28 +00:00
cities-internet	Resolve a composite's child bundles against the tree root, not a guessed depth	2026-09-23 19:34:28 +00:00
country-posters	Resolve the shared asset base per bundle, so nested tabs stop 404ing	2026-09-23 12:14:52 +00:00
dashboard-plus-grid	Add the Gospel Access filter, the ladder the binary flag was flattening	2026-09-23 13:19:22 +00:00
demo-map	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
doxa-maps-spa	Regions mounts its cap-4 composite; UPG-100 drops its duplicate share and shrinks its dots	2026-09-23 19:37:55 +00:00
doxa-research-map	Widen the red ramp, add a greyscale ramp, and gate cap-4 interoperability	2026-09-23 14:53:51 +00:00
doxa-simple-map	Describe every plugin: 15 of 26 profiles shipped with no description	2026-09-22 03:11:07 +00:00
doxa-vision-card	Brand-neutral shared VerticalTabsLayout with lazy nested-element hosting; fix cap-5 prayer tab leaf path; neutralize library identifiers; add Forgejo CI build-gate workflow	2026-09-19 17:24:30 +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-resources	Resolve a composite's child bundles against the tree root, not a guessed depth	2026-09-23 19:34:28 +00:00
key-cities	Resolve the shared asset base per bundle, so nested tabs stop 404ing	2026-09-23 12:14:52 +00:00
my-upg-100-list	Regions mounts its cap-4 composite; UPG-100 drops its duplicate share and shrinks its dots	2026-09-23 19:37:55 +00:00
people-groups-grid	Add the Gospel Access filter, the ladder the binary flag was flattening	2026-09-23 13:19:22 +00:00
plugin-studio	Plugin studio: show what a composite is made of, in one panel	2026-09-23 20:21:48 +00:00
prayer-walk-planner	Add prayer-walk-planner: experimental polygon prayer-walking map	2026-09-23 16:22:56 +00:00
regions-dashboard	Regions element gets the Select View tabs, shared with UPG-100	2026-09-23 19:08:00 +00:00
research-dashboard	Full table headers via horizontal scroll, and a full-screen table	2026-09-23 20:25:08 +00:00
research-map-plus-grid	Share the mobile composite too, and make the url absolute so the embed works	2026-09-23 08:32:50 +00:00
stack-demo	Let a stacked composite find its siblings in either tree	2026-09-22 15:37:41 +00:00
template-bundle	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +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	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +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/doxa-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="/doxa-maps/<your-map>/<your-map>.js"></script>
<doxa-map profile-config='{"profile":"overview","tk":"pk.eyJ..."}'></doxa-map>
<doxa-map profile-config='{"profile":"detail","tk":"pk.eyJ..."}'></doxa-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/doxa-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).