@fundar/data-chart-telling 0.0.63 → 1.0.0

package/dist/plots/utils/declutter.d.ts

@@ -1,120 +0,0 @@
-export type Declutter1DResult<T> = {
-    /** Sorted input, each with `.pos` replaced by its decluttered position. */
-    positions: T[];
-    /**
-     * `connected[i]` is true when `positions[i]` and `positions[i + 1]` were
-     * actually pushed apart by the algorithm — either the down-pass pushed
-     * `i + 1` down because of `i`, or the up-pass pulled `i` up because of
-     * `i + 1`. `length === positions.length - 1`.
-     */
-    connected: boolean[];
-};
-/**
- * Spreads a set of pixel-space positions apart along one axis so that no two
- * end up closer than `minGap`, while keeping the overall block centered on
- * the original positions. Computes two independent, individually-valid
- * arrangements — a forward pass that only ever pushes items *down* to clear
- * the one above it, and a backward pass that only ever pushes items *up* to
- * clear the one below — then averages them index-by-index.
- *
- * A pass chained directly onto the other's output (push down, *then* pull up
- * on the already-pushed result) is a no-op: by the time the down-pass
- * finishes, `sorted[i] >= sorted[i-1] + minGap` already holds everywhere,
- * which is exactly the condition an up-pass would otherwise "fix". Averaging
- * two independent passes instead is what actually centers the block; it
- * still keeps every adjacent gap >= minGap, since each pass's own gaps are
- * already >= minGap and the average of two such gaps is too.
- *
- * Also records, per adjacent pair, whether either pass actually had to push
- * — the ground truth for "did these two really interact," which
- * `laneAssignment` needs and can't reliably reconstruct from positions alone
- * after the fact (see its own doc comment).
- *
- * `bounds`, if given, keeps every *run* (a maximal stretch of connected
- * items — lone, unconnected items are left at their true position
- * regardless) inside `[lo, hi]`: nothing pushed apart by this function is
- * ever allowed to end up off the edge of whatever pixel range the caller
- * considers in-bounds (typically the plot's own content box). A run that
- * already fits is only shifted, never resized; a run too big to fit even
- * at its natural spacing is shrunk just enough to fit, uniformly, so it's
- * still evenly spaced — just tighter than `minGap` calls for. See
- * `fitRunsWithinBounds` for the actual shift/shrink math.
- *
- * `bounds` also biases *which* pass a run's average leans on, via
- * {@link runBiasWeights}: a run sitting close to one edge has little slack on
- * that side, so a plain 50/50 blend would still ask the up-pass and
- * down-pass to pull the block symmetrically toward *both* edges before
- * `fitRunsWithinBounds` shifts/shrinks it back — the up-pass reaching for
- * room that was never really there, needlessly widening how far members end
- * up travelling from their original positions (`laneAssignment`'s own lane
- * count grows with exactly that travel distance — see its doc comment) — so
- * a run near an edge leans toward whichever pass already grows away from it
- * instead — the block still expands to clear `minGap` everywhere, just
- * mostly in the one direction that was actually available, the way a person
- * sliding books apart on a shelf pinned against one wall would.
- */
-export declare function declutter1D<T extends {
-    pos: number;
-}>(items: T[], minGap: number, bounds?: readonly [number, number]): Declutter1DResult<T>;
-/**
- * Groups `declutter1D`'s own `connected` flags into runs (maximal stretches
- * of consecutive connected pairs), then gives every run member its own,
- * unique lane — no two members ever share one, deliberately (see below) —
- * ordered so that a leader line drawn through lane `rank` never crosses, or
- * even draws visually flush against, one drawn through any other lane of
- * the same run.
- *
- * Every member's leader line is the same three-segment elbow: a horizontal
- * stub from the data point out to its lane, a vertical run up/down that
- * lane to the label's height, then a final horizontal run in to the shared
- * label column. Two such elbows, `i` (in the tighter of the two lanes) and
- * `j` (further out), are safe from crossing *specifically* when neither of
- * these can happen:
- * - `j`'s own stub (at `j`'s original height) reaches out past `i`'s lane
- *   while `i`'s vertical run passes through that height — `j`'s stub would
- *   cut across `i`'s vertical segment.
- * - `i`'s final run (at `i`'s label height) reaches past `i`'s own lane out
- *   to the shared column, and in doing so crosses `j`'s lane while `j`'s
- *   vertical run passes through *that* height — `i`'s own final segment
- *   would cut across `j`'s vertical segment.
- *
- * Whether `i` can safely take the tighter lane depends on both members'
- * *actual* pixel geometry — not simply on which one moved further — so each
- * pair is checked directly per {@link saferNearer} rather than inferred from
- * a single sort key. A pair with a clean, provable answer either way (the
- * overwhelmingly common case for `declutter1D`'s own output) is ordered by
- * that answer; a pair with no clean answer (both directions equally
- * "unsafe," or, symmetrically, both fine) falls back to the same *travel
- * distance* heuristic used before this per-pair check existed — furthest
- * `|final - original|` first — which is what decides ties and keeps the
- * "furthest traveller gets the tightest lane, so it starts bending
- * immediately rather than reaching across everyone else's leader lines
- * first" intent for every pair the geometry itself doesn't already settle.
- *
- * No sharing, ever, is the other half of this: two members can only have
- * non-overlapping travel spans (and so pass the old, now-removed,
- * share-a-lane check) by sitting far apart along the axis — but "far apart"
- * is exactly the case with the most room to spare, so it never needed the
- * lane it would save by sharing, while any pair close enough to actually be
- * short on room has spans close enough together that sharing draws their
- * two leader lines only a couple pixels apart — visually indistinguishable
- * from one continuous line touching the next label down. A run of `n`
- * members uses exactly `n` lanes; letting the lane count grow is the price
- * of a fan that never has two leader lines touching *or* crossing, and
- * `ValueLabels`' own auto-margin measurement (see its doc comment) already
- * grows `margins.right` to fit however many lanes that turns out to be, so
- * nothing has to be guessed up front.
- *
- * `rank` is the lane index (0-indexed) to drive a leader line's routing:
- * `rank` 0 bends right off the data point (a short first stub); higher
- * ranks travel further before bending (right up to the shared label
- * column). `lanesUsed` is the run's own total lane count — always equal to
- * `runSize` — shared by every member; `runSize` is the run's member count,
- * for callers that just need to know whether a given member belongs to a
- * real run at all.
- */
-export declare function laneAssignment(originals: number[], finals: number[], connected: boolean[]): {
-    rank: number;
-    lanesUsed: number;
-    runSize: number;
-}[];

package/dist/plots/utils/declutter.js

@@ -1,240 +0,0 @@
-/**
- * Spreads a set of pixel-space positions apart along one axis so that no two
- * end up closer than `minGap`, while keeping the overall block centered on
- * the original positions. Computes two independent, individually-valid
- * arrangements — a forward pass that only ever pushes items *down* to clear
- * the one above it, and a backward pass that only ever pushes items *up* to
- * clear the one below — then averages them index-by-index.
- *
- * A pass chained directly onto the other's output (push down, *then* pull up
- * on the already-pushed result) is a no-op: by the time the down-pass
- * finishes, `sorted[i] >= sorted[i-1] + minGap` already holds everywhere,
- * which is exactly the condition an up-pass would otherwise "fix". Averaging
- * two independent passes instead is what actually centers the block; it
- * still keeps every adjacent gap >= minGap, since each pass's own gaps are
- * already >= minGap and the average of two such gaps is too.
- *
- * Also records, per adjacent pair, whether either pass actually had to push
- * — the ground truth for "did these two really interact," which
- * `laneAssignment` needs and can't reliably reconstruct from positions alone
- * after the fact (see its own doc comment).
- *
- * `bounds`, if given, keeps every *run* (a maximal stretch of connected
- * items — lone, unconnected items are left at their true position
- * regardless) inside `[lo, hi]`: nothing pushed apart by this function is
- * ever allowed to end up off the edge of whatever pixel range the caller
- * considers in-bounds (typically the plot's own content box). A run that
- * already fits is only shifted, never resized; a run too big to fit even
- * at its natural spacing is shrunk just enough to fit, uniformly, so it's
- * still evenly spaced — just tighter than `minGap` calls for. See
- * `fitRunsWithinBounds` for the actual shift/shrink math.
- *
- * `bounds` also biases *which* pass a run's average leans on, via
- * {@link runBiasWeights}: a run sitting close to one edge has little slack on
- * that side, so a plain 50/50 blend would still ask the up-pass and
- * down-pass to pull the block symmetrically toward *both* edges before
- * `fitRunsWithinBounds` shifts/shrinks it back — the up-pass reaching for
- * room that was never really there, needlessly widening how far members end
- * up travelling from their original positions (`laneAssignment`'s own lane
- * count grows with exactly that travel distance — see its doc comment) — so
- * a run near an edge leans toward whichever pass already grows away from it
- * instead — the block still expands to clear `minGap` everywhere, just
- * mostly in the one direction that was actually available, the way a person
- * sliding books apart on a shelf pinned against one wall would.
- */
-export function declutter1D(items, minGap, bounds) {
-    const sorted = [...items].sort((a, b) => a.pos - b.pos);
-    const n = sorted.length;
-    const connected = new Array(Math.max(0, n - 1)).fill(false);
-    const down = sorted.map((d) => d.pos);
-    for (let i = 1; i < n; i++) {
-        const pushed = down[i - 1] + minGap;
-        if (pushed > down[i]) {
-            down[i] = pushed;
-            connected[i - 1] = true;
-        }
-    }
-    const up = sorted.map((d) => d.pos);
-    for (let i = n - 2; i >= 0; i--) {
-        const pulled = up[i + 1] - minGap;
-        if (pulled < up[i]) {
-            up[i] = pulled;
-            connected[i] = true;
-        }
-    }
-    const weights = bounds ? runBiasWeights(down, up, connected, bounds) : sorted.map(() => 0.5);
-    const averaged = sorted.map((_, i) => down[i] * weights[i] + up[i] * (1 - weights[i]));
-    const fitted = bounds ? fitRunsWithinBounds(averaged, connected, bounds) : averaged;
-    const positions = sorted.map((d, i) => ({ ...d, pos: fitted[i] }));
-    return { positions, connected };
-}
-/**
- * Per-run blend weight (applied to the down-pass; `1 - weight` goes to the
- * up-pass) favouring whichever pass already grows away from the nearer edge
- * — see {@link declutter1D}'s doc comment for why. `0.5` (the down/up
- * midpoint, i.e. no bias) when a run's naturally-centred span has roughly
- * equal room on both sides; sliding toward `1` (all down-pass) as room above
- * vanishes, toward `0` (all up-pass) as room below vanishes. Every member of
- * a run gets the *same* weight — the point is the block moving as one
- * (mostly) one-directional piece, not each member picking its own bias.
- */
-function runBiasWeights(down, up, connected, [lo, hi]) {
-    const weights = down.map(() => 0.5);
-    let i = 0;
-    while (i < down.length) {
-        let j = i;
-        while (j < connected.length && connected[j])
-            j++;
-        if (j > i) {
-            const center = ((down[i] + up[i]) / 2 + (down[j] + up[j]) / 2) / 2;
-            const roomAbove = Math.max(0, center - lo);
-            const roomBelow = Math.max(0, hi - center);
-            const total = roomAbove + roomBelow;
-            const weight = total > 0 ? roomBelow / total : 0.5;
-            for (let k = i; k <= j; k++)
-                weights[k] = weight;
-        }
-        i = j + 1;
-    }
-    return weights;
-}
-/**
- * Shifts, and shrinks only if it must, each run of `connected` positions so
- * it lands entirely inside `[lo, hi]`. A run's own relative spacing is
- * preserved as-is (just translated) whenever it already fits in `hi - lo`;
- * only a run wider than the available space gets uniformly scaled down
- * around its centre first. A lone, unconnected position is simply clamped
- * to the nearer bound instead — its own value never needed decluttering,
- * but it can still sit close enough to the scale's own edge to overflow on
- * its own.
- */
-function fitRunsWithinBounds(positions, connected, [lo, hi]) {
-    const out = [...positions];
-    const available = hi - lo;
-    let i = 0;
-    while (i < out.length) {
-        let j = i;
-        while (j < connected.length && connected[j])
-            j++;
-        if (j > i) {
-            const runMin = out[i];
-            const runMax = out[j];
-            if (runMin < lo || runMax > hi) {
-                const naturalSpan = runMax - runMin;
-                const scale = naturalSpan > 0 ? Math.min(1, available / naturalSpan) : 1;
-                const idealCenter = (runMin + runMax) / 2;
-                const newSpan = naturalSpan * scale;
-                const newCenter = Math.min(Math.max(idealCenter, lo + newSpan / 2), hi - newSpan / 2);
-                for (let k = i; k <= j; k++) {
-                    out[k] = newCenter + (out[k] - idealCenter) * scale;
-                }
-            }
-        }
-        else {
-            out[i] = Math.min(Math.max(out[i], lo), hi);
-        }
-        i = j + 1;
-    }
-    return out;
-}
-/**
- * Groups `declutter1D`'s own `connected` flags into runs (maximal stretches
- * of consecutive connected pairs), then gives every run member its own,
- * unique lane — no two members ever share one, deliberately (see below) —
- * ordered so that a leader line drawn through lane `rank` never crosses, or
- * even draws visually flush against, one drawn through any other lane of
- * the same run.
- *
- * Every member's leader line is the same three-segment elbow: a horizontal
- * stub from the data point out to its lane, a vertical run up/down that
- * lane to the label's height, then a final horizontal run in to the shared
- * label column. Two such elbows, `i` (in the tighter of the two lanes) and
- * `j` (further out), are safe from crossing *specifically* when neither of
- * these can happen:
- * - `j`'s own stub (at `j`'s original height) reaches out past `i`'s lane
- *   while `i`'s vertical run passes through that height — `j`'s stub would
- *   cut across `i`'s vertical segment.
- * - `i`'s final run (at `i`'s label height) reaches past `i`'s own lane out
- *   to the shared column, and in doing so crosses `j`'s lane while `j`'s
- *   vertical run passes through *that* height — `i`'s own final segment
- *   would cut across `j`'s vertical segment.
- *
- * Whether `i` can safely take the tighter lane depends on both members'
- * *actual* pixel geometry — not simply on which one moved further — so each
- * pair is checked directly per {@link saferNearer} rather than inferred from
- * a single sort key. A pair with a clean, provable answer either way (the
- * overwhelmingly common case for `declutter1D`'s own output) is ordered by
- * that answer; a pair with no clean answer (both directions equally
- * "unsafe," or, symmetrically, both fine) falls back to the same *travel
- * distance* heuristic used before this per-pair check existed — furthest
- * `|final - original|` first — which is what decides ties and keeps the
- * "furthest traveller gets the tightest lane, so it starts bending
- * immediately rather than reaching across everyone else's leader lines
- * first" intent for every pair the geometry itself doesn't already settle.
- *
- * No sharing, ever, is the other half of this: two members can only have
- * non-overlapping travel spans (and so pass the old, now-removed,
- * share-a-lane check) by sitting far apart along the axis — but "far apart"
- * is exactly the case with the most room to spare, so it never needed the
- * lane it would save by sharing, while any pair close enough to actually be
- * short on room has spans close enough together that sharing draws their
- * two leader lines only a couple pixels apart — visually indistinguishable
- * from one continuous line touching the next label down. A run of `n`
- * members uses exactly `n` lanes; letting the lane count grow is the price
- * of a fan that never has two leader lines touching *or* crossing, and
- * `ValueLabels`' own auto-margin measurement (see its doc comment) already
- * grows `margins.right` to fit however many lanes that turns out to be, so
- * nothing has to be guessed up front.
- *
- * `rank` is the lane index (0-indexed) to drive a leader line's routing:
- * `rank` 0 bends right off the data point (a short first stub); higher
- * ranks travel further before bending (right up to the shared label
- * column). `lanesUsed` is the run's own total lane count — always equal to
- * `runSize` — shared by every member; `runSize` is the run's member count,
- * for callers that just need to know whether a given member belongs to a
- * real run at all.
- */
-export function laneAssignment(originals, finals, connected) {
-    const n = connected.length + 1;
-    const out = Array.from({ length: n }, () => ({ rank: 0, lanesUsed: 1, runSize: 1 }));
-    const span = (k) => {
-        const a = originals[k];
-        const b = finals[k];
-        return a < b ? [a, b] : [b, a];
-    };
-    const distance = (k) => Math.abs(finals[k] - originals[k]);
-    /** Whether lane-`i`-nearer-than-`j` is provably crossing-free — see this function's doc comment. */
-    function saferNearer(i, j) {
-        const [loI, hiI] = span(i);
-        const [loJ, hiJ] = span(j);
-        const jStubCutsI = originals[j] >= loI && originals[j] <= hiI;
-        const iFinalCutsJ = finals[i] >= loJ && finals[i] <= hiJ;
-        return !jStubCutsI && !iFinalCutsJ;
-    }
-    let i = 0;
-    while (i < n) {
-        let j = i;
-        while (j < connected.length && connected[j])
-            j++;
-        const runSize = j - i + 1;
-        if (runSize > 1) {
-            // Members of this run, ordered so each is provably safe to place
-            // nearer than the next whenever that's decidable, furthest-travelled
-            // first otherwise (ties keep their original — i.e. top-to-bottom —
-            // order, since `sort` is stable). Position in this order *is* the
-            // rank: no sharing.
-            const order = Array.from({ length: runSize }, (_, k) => i + k).sort((a, b) => {
-                const aNearer = saferNearer(a, b);
-                const bNearer = saferNearer(b, a);
-                if (aNearer !== bNearer)
-                    return aNearer ? -1 : 1;
-                return distance(b) - distance(a);
-            });
-            order.forEach((k, rank) => {
-                out[k] = { rank, lanesUsed: runSize, runSize };
-            });
-        }
-        i = j + 1;
-    }
-    return out;
-}

package/dist/plots/utils/labelOverflow.svelte.d.ts

@@ -1,107 +0,0 @@
-import type { MarginConfig } from '../../types/plots/props';
-/** How far a value label's rendered box extends past the plot's own content box, in pixels, on each side (0 = no overflow). */
-export type MarginOverflow = {
-    left: number;
-    right: number;
-    top: number;
-    bottom: number;
-};
-/**
- * A generic `maxOverflow` cap for {@link createLabelMarginTracker}: half of
- * each dimension, so a facet cramped enough that its own value label can
- * never fully fit still leaves the plot's own content box the other half,
- * rather than `measured` growing without bound (see that function's own
- * `maxOverflow` doc comment). The same backstop applies regardless of *what*
- * overflows or *why* — every value-label-drawing plot (line/bar/pyramid/
- * scatter) passes this, sized off its own `width`/`height`.
- */
-export declare function halfDimensionOverflowCap(width: number, height: number): MarginOverflow;
-/**
- * Watches an SVG group's rendered bounding box against the plot's own
- * content box (`bounds`) and reports how far it overflows on each side.
- * Polled across successive paints until two consecutive readings agree,
- * rather than trusted after a single frame: the group's own resolved
- * geometry (driven by svelteplot's separate reactive graph) and svelteplot's
- * own axis auto-margins can take a variable number of frames to settle —
- * more on a page with many other components competing for layout (e.g. a
- * docs page) than in an isolated story. Measuring too early can catch
- * content still at its pre-layout default position; capped so a layout that
- * genuinely never stabilizes still reports its last reading instead of
- * polling forever. Also waits for web fonts to finish loading, since glyph
- * metrics (and therefore `getBBox()`) can still reflect a fallback font's
- * narrower widths until the real font swaps in.
- */
-export declare function watchLabelOverflow(args: {
-    el: () => SVGGElement | undefined;
-    bounds: () => {
-        left: number;
-        right: number;
-        top: number;
-        bottom: number;
-    } | undefined;
-    onOverflow: (overflow: MarginOverflow) => void;
-}): void;
-/**
- * Tracks value-label overflow reported by (possibly several, e.g. one per
- * series) {@link watchLabelOverflow} calls and grows a local margin override
- * to fit it — monotonically, since shrinking it back would re-expose the
- * overflow that caused the growth in the first place, oscillating between
- * "shrink margin → overflow reappears → grow margin → …". Each side is only
- * ever set when the caller's own `margins` prop hasn't already pinned it, so
- * an explicit caller override always wins over this auto-grown one.
- *
- * That monotonic growth is only sound for a *stable* dataset — it assumes
- * every reading describes the same thing being measured, just possibly at an
- * earlier, not-yet-settled frame. It stops being sound once the caller's own
- * data changes identity underneath it (e.g. a timeline scrubber revealing a
- * different slice of rows on every tick): an overflow measured against
- * *that* frame's rendered labels doesn't describe the next frame's, so
- * carrying it forward forever can leave a plot permanently — and wrongly —
- * margin-inflated by whatever the single most cluttered frame it ever
- * passed through needed, long after scrubbing away from it. `resetKey`, if
- * given, is compared by identity on every call; a change drops `measured`
- * back to zero so the next frame's overflow is measured fresh against only
- * what's actually on screen now. Pass whatever reactive value identifies
- * "what's currently being plotted" for the caller (e.g. its own resolved
- * series list) — a plain reference/value comparison, not a deep one, so it
- * only need change identity when the rendered content actually does.
- */
-export declare function createLabelMarginTracker(margins: () => MarginConfig | undefined, resetKey?: () => unknown, 
-/**
- * A precomputed overflow estimate — from the full dataset, not just the
- * current frame — used as the reset target instead of zero. Since it's
- * derived from stable inputs, a `resetKey` change resets `measured` back
- * to roughly the same value instead of zero, so DOM growth rarely needs
- * to re-detect and re-grow it (which would otherwise remount the plot on
- * every reset). DOM measurement can still grow past it for whatever this
- * estimate doesn't cover.
- */
-floor?: () => MarginOverflow, 
-/**
- * Ceiling on how far `measured` can grow on each side, independent of
- * `floor`. Without one, a cell too small to ever fully fit its own label
- * (e.g. a narrow facet) keeps reporting overflow after every growth-
- * triggered remount — since the label's absolute size never shrinks —
- * and `measured` grows without bound, eventually leaving nothing for the
- * plot's own content box. Capping it trades a permanently-clipped label
- * in that case for a plot that still renders. Pass `Infinity` on a side
- * (the default) to leave it uncapped.
- */
-maxOverflow?: () => MarginOverflow): {
-    report: (overflow: MarginOverflow) => void;
-    readonly resolvedMargins: Partial<{
-        top: number | "auto";
-        right: number | "auto";
-        bottom: number | "auto";
-        left: number | "auto";
-    }> | undefined;
-    readonly plotProps: {
-        margins: Partial<{
-            top: number | "auto";
-            right: number | "auto";
-            bottom: number | "auto";
-            left: number | "auto";
-        }> | undefined;
-        marginRemountKey: string;
-    };
-};