@gjsify/adwaita-nativescript 0.36.0 → 0.38.0

package/lib/types/widgets/chrome.d.ts

@@ -17,10 +17,8 @@ export declare function defaultClampProps(): ClampProps;
 /**
  * Normalise one clamp property, keeping a nonsense value out of the layout.
  *
- * Delegates to core so the NativeScript widget and the browser element agree on
- * the three inputs they used to answer differently — `0` (valid, and NOT the
- * default), a non-numeric value (never reaches the layout, so the DEFAULT
- * applies), and a negative (clamped to the range floor).
+ * The three inputs worth knowing: `0` is valid and NOT the default, a non-numeric
+ * value falls back to the DEFAULT, a negative is clamped to the range floor.
  */
 export declare function normalizeClampProp(value: number | string | null | undefined, fallback: number): number;
 /** What one clamp layout pass tells the widget to do with its child. */
@@ -37,55 +35,41 @@ export interface ClampAllocationForWidth {
 /**
  * The child width and size class for a clamp `availableWidth` DIPs wide.
  *
- * `availableWidth <= 0` means NativeScript has not laid the view out yet — it
- * reports a zero size before the first pass — and the honest answer there is
- * "do not constrain", the same shape `sidebarWidthFor` uses for the same reason.
- * Anything else runs libadwaita's curve, so a narrow container yields a narrow
- * child rather than the maximum.
+ * `availableWidth <= 0` means NativeScript has not laid the view out yet (it
+ * reports a zero size before the first pass), and the honest answer there is "do
+ * not constrain" — the same shape `sidebarWidthFor` uses for the same reason.
  *
  * `childMin`/`childNat` are 0: NativeScript does not expose a child's measured
  * minimum before layout, and `lower = MAX (…, child_min)` only ever RAISES the
- * child's width — an NS child whose own content is wider than the clamp already
- * overflows rather than being cut, so nothing is lost by leaving it out.
+ * child's width — an NS child wider than the clamp already overflows rather than
+ * being cut, so nothing is lost by leaving it out.
  */
 export declare function clampAllocationFor(availableWidth: number, props: ClampProps): ClampAllocationForWidth;
-/**
- * Default spinner diameter in DIPs — `Adw.Spinner`'s measured natural size,
- * which equals its minimum (adw-spinner.c:78-81).
- *
- * Replaces an invented 32: nothing in libadwaita produces that number.
- */
+/** Default spinner diameter in DIPs — `Adw.Spinner`'s natural size, which equals its minimum. */
 export declare const DEFAULT_SPINNER_SIZE = 16;
 /**
  * The RING diameter for a requested BOX size — floored at the measured minimum
  * 16 and capped at Adwaita's 64, with the odd-size flooring (`31` draws a 30 DIP
  * ring) coming from the paintable rather than from here.
  *
- * The two are different numbers, which is the whole point: `AdwSpinner` sizes
- * its BOX to the request and its `ActivityIndicator` to this. They used to be
- * one, so `size = 200` occupied 64 DIPs of layout where GTK occupies 200.
+ * Box and ring are deliberately different numbers: `AdwSpinner` sizes its BOX to
+ * the request and its `ActivityIndicator` to this, so `size = 200` occupies 200
+ * DIPs of layout around a 64 DIP ring.
  */
 export declare function spinnerDiameter(value: number | string | null | undefined): number;
 /** The four toolbar-view properties the style classes are derived from. */
 export interface ToolbarViewProps {
-    /** `top-bar-style`. */
     topBarStyle: AdwToolbarStyle;
-    /** `bottom-bar-style`. */
     bottomBarStyle: AdwToolbarStyle;
-    /** `extend-content-to-top-edge`. */
     extendContentToTopEdge: boolean;
-    /** `extend-content-to-bottom-edge`. */
     extendContentToBottomEdge: boolean;
 }
 /** The property defaults a fresh toolbar view starts with. */
 export declare function defaultToolbarViewProps(): ToolbarViewProps;
 /** The three `className` strings a toolbar view distributes over its own node and its two bar boxes. */
 export interface ToolbarViewClassNames {
-    /** `className` for the view. */
     view: string;
-    /** `className` for the top-bar box. */
     topBar: string;
-    /** `className` for the bottom-bar box. */
     bottomBar: string;
 }
 /**
@@ -105,42 +89,33 @@ export declare function clampChildClassName(current: string, sizeClass: AdwClamp
 export type BannerProps = AdwBannerProps;
 /**
  * The property defaults a fresh banner starts with — libadwaita's, not this
- * port's.
- *
- * This is the whole reason the banner is here. `AdwBanner` used to initialise
- * `_revealed = true` AND never write `visibility` in its constructor, so a
- * banner put itself on screen on a device while the same markup stayed hidden in
- * the browser. `Adw.Banner:revealed` defaults to FALSE (adw-banner.c:456-459) —
- * "Banners are hidden by default" (:47) — and `use-markup` to TRUE (:422-425),
- * which the port had backwards as well.
+ * port's. The two easy ones to get backwards: `Adw.Banner:revealed` defaults to
+ * FALSE (banners are hidden until revealed) and `use-markup` to TRUE.
  */
 export declare function defaultBannerProps(): BannerProps;
 /**
  * The text the NS title `Label` is given.
  *
- * `Adw.Banner`'s title is Pango markup by default (:422-425) and the NS CSS
- * subset has no inline-markup layer at all, so the honest reduction is the
- * markup's PLAIN TEXT: `<b>Metered</b>` reads `Metered`, which is what GTK
- * paints minus the weight, where writing the raw string would paint the tags.
- * Unparseable markup keeps the raw string, reproducing the C fallback that
- * {@link stripMarkup} already models.
+ * `Adw.Banner`'s title is Pango markup by default and the NS CSS subset has no
+ * inline-markup layer, so the honest reduction is the markup's PLAIN TEXT:
+ * `<b>Metered</b>` reads `Metered`, where the raw string would paint the tags.
+ * Unparseable markup keeps the raw string, reproducing the C fallback.
  */
 export declare function bannerTitleText(title: string, useMarkup: boolean): string;
 /**
  * The NS `visibility` for a `revealed` value.
  *
- * `Adw.Banner` reveals through a `GtkRevealer` (:817); the NS subset has no
- * revealer, so `collapse` — which takes the view out of layout entirely — is the
- * closest thing to a fully retracted one.
+ * `Adw.Banner` reveals through a `GtkRevealer`; the NS subset has none, so
+ * `collapse` — which takes the view out of layout entirely — is the closest thing
+ * to a fully retracted one.
  */
 export declare function bannerVisibility(revealed: boolean): 'visible' | 'collapse';
 /**
  * The `className` for the banner button — the managed `button-style` class
  * swapped in, every other token left alone.
  *
- * `adw_banner_set_button_style` only ever adds or removes `suggested-action`
- * (:766, :769); it never rewrites the button's class list, and neither does
- * this.
+ * `adw_banner_set_button_style` only ever adds or removes `suggested-action`; it
+ * never rewrites the button's class list, and neither does this.
  */
 export declare function bannerButtonClassName(current: string, style: AdwBannerButtonStyle): string;
 /**

package/lib/types/widgets/data-grid-model.d.ts

@@ -2,9 +2,8 @@ import type { AdwDataGridRowVariant, DataGridTrack } from '@gjsify/adwaita-core'
 import type { GridUnitType } from '@nativescript/core';
 /** The two numbers a NativeScript `ItemSpec` is constructed from. */
 export interface DataGridItemSpec {
-    /** The `ItemSpec` value: a star weight, a pixel length, or 1 for `auto`. */
+    /** A star weight, a pixel length, or 1 for `auto`. */
     value: number;
-    /** The `GridUnitType` — `'star'`, `'pixel'` or `'auto'`. */
     type: GridUnitType;
 }
 /** The class the header row's background carries. */
@@ -20,18 +19,15 @@ export declare const DATA_GRID_HEADER_CELL_CLASS = "header-cell";
  * `DataGridTrack`'s `fixed` kind carries the author's `width` string verbatim,
  * because only a CSS engine can resolve every unit CSS has. NativeScript has
  * exactly one length unit — the DIP — and its own stylesheet subset writes it as
- * a bare number (`min-height: 34`, `padding: 5 10 5 10`), so BOTH `'80px'` and
- * `'80'` are read as 80 here and everything else (`6rem`, `50%`, `calc(...)`)
- * is unresolvable and falls back to a content-sized track.
+ * a bare number (`min-height: 34`), so BOTH `'80px'` and `'80'` are read as 80
+ * here and everything else (`6rem`, `50%`, `calc(...)`) falls back to a
+ * content-sized track.
  *
- * That bare-number acceptance is a deliberate divergence from the browser, where
- * `width: '80'` is not a valid CSS length and takes the WHOLE
- * `grid-template-columns` declaration down with it. Falling back to `auto` for
- * one column is the smaller failure, and refusing a spelling that is valid in
- * this renderer's own stylesheet would be the surprising half.
- *
- * A negative or non-finite length is rejected rather than clamped: `ItemSpec`
- * refuses one, and a column silently pinned to 0 reads as a missing column.
+ * Accepting a bare number diverges from the browser deliberately, where `width:
+ * '80'` is not a valid CSS length and takes the whole `grid-template-columns`
+ * declaration down with it; falling back to `auto` for one column is the smaller
+ * failure. A negative or non-finite length is rejected rather than clamped:
+ * `ItemSpec` refuses one, and a column silently pinned to 0 reads as missing.
  */
 export declare function parseDataGridWidth(css: string): number | null;
 /**
@@ -54,14 +50,11 @@ export declare function dataGridItemSpec(track: DataGridTrack): DataGridItemSpec
 /**
  * A stable key for a track list — what the widget re-declares its columns on.
  *
- * The precedent is `AdwViewSwitcherBar`, which rebuilds its buttons only when the
- * page COUNT moves so that a selection change cannot replace the button under
- * the user's finger. The same discipline applies here, with one difference the
- * grid forces: a column list can change WITHOUT changing length — pinning a
- * column's `width` on a narrow screen is exactly that — and a count guard would
- * keep painting against the old tracks. So the guard is the tracks themselves,
- * which is a strict superset: whenever the count moves the key moves too, and a
- * repaint (new rows, a toggled `interactive`) never touches the columns.
+ * The guard is the tracks themselves, not their COUNT: a column list can change
+ * without changing length (pinning a column's `width` on a narrow screen does
+ * exactly that) and a count guard would keep painting against the old tracks.
+ * Whenever the count moves the key moves too, and a repaint (new rows, a toggled
+ * `interactive`) never touches the columns.
  */
 export declare function dataGridTracksKey(tracks: ReadonlyArray<DataGridTrack>): string;
 /**
@@ -76,12 +69,12 @@ export declare function dataGridShapeKey(columnCount: number, rowCount: number):
 /**
  * The classes a data row's background carries.
  *
- * The row background is a NativeScript-only node and this is why it exists: the
- * browser paints the fill, the hairline rules and the hover affordance on the
- * row ELEMENT, which is a real element there because it is a subgrid. Here the
- * cells are direct children of the one grid, so a full-width `StackLayout`
- * placed first at the same row — below the cells, spanning every column — is
- * what carries them, plus the tap target and the press feedback.
+ * The row background is a NativeScript-only node: the browser paints the fill, the
+ * hairline rules and the hover affordance on the row ELEMENT, which is a real
+ * element there because it is a subgrid. Here the cells are direct children of the
+ * one grid, so a full-width `StackLayout` placed first at the same row — below the
+ * cells, spanning every column — carries them plus the tap target and press
+ * feedback.
  *
  * `interactive` is a class rather than a widget flag so the press-darken keys off
  * it: `attachRowPressFeedback` is wired on EVERY data row, and a non-interactive
@@ -91,14 +84,10 @@ export declare function dataGridRowClass(variant: AdwDataGridRowVariant, interac
 /**
  * The classes a body cell carries: its column's own, plus the row's variant.
  *
- * The variant is repeated onto the CELL because of the same structural
- * difference: the browser bolds a subtotal's figures with
- * `.variant-subtotal .adw-data-grid-cell`, a DESCENDANT selector, and here the
- * cell is not inside the row background — the two are siblings in one grid. So
- * the row class cannot reach the cells and the cell has to say it itself.
- *
- * `normal` adds nothing: it is every row in a statement but the handful that
- * carry emphasis, and a class the stylesheet has no rule for is only noise in
- * the one place a reader looks when the emphasis is wrong.
+ * The variant is repeated onto the CELL because the browser bolds a subtotal's
+ * figures with a DESCENDANT selector (`.variant-subtotal .adw-data-grid-cell`)
+ * while here cell and row background are SIBLINGS in one grid — the row class
+ * cannot reach the cells. `normal` adds nothing, since the stylesheet has no rule
+ * for it.
  */
 export declare function dataGridCellClass(columnClasses: ReadonlyArray<string>, variant: AdwDataGridRowVariant): string;

package/lib/types/widgets/index.d.ts

@@ -43,6 +43,12 @@ export { AdwSplitButton, CLICKED, MENU_TAPPED } from './adw-split-button.js';
 export type { MenuTappedEventData } from './adw-split-button.js';
 export { AdwToggleGroup, NOTIFY_SELECTED as NOTIFY_TOGGLE_SELECTED, ToggleGroupState } from './adw-toggle-group.js';
 export type { NotifyToggleSelectedEventData, ToggleGroupStateChange, ToggleGroupStateListener, } from './adw-toggle-group.js';
+export { applyAdwaitaNsAccent, clearAdwaitaNsAccent } from './adw-accent.js';
+export { ADWAITA_NS_ACCENT_RULES, adwaitaNsAccentColor, adwaitaNsAccentCss } from './accent-theme.js';
+export type { AccentRole, AccentRule } from './accent-theme.js';
+export { AdwShortcutLabel } from './adw-shortcut-label.js';
+export { SHORTCUT_LABEL_CAP_TEXT_CLASS, SHORTCUT_LABEL_CLASS, SHORTCUT_LABEL_DIMMED_CLASS, SHORTCUT_LABEL_DISABLED_CLASS, SHORTCUT_LABEL_KEYCAP_CLASS, SHORTCUT_LABEL_KEYS_CLASS, SHORTCUT_LABEL_SIDE_CLASS, SHORTCUT_LABEL_SPACED_CLASS, shortcutLabelDirection, shortcutLabelPlatform, shortcutLabelRenderPlan, } from './shortcut-label.js';
+export type { ShortcutLabelRenderPlan, ShortcutLabelViewSpec } from './shortcut-label.js';
 export { AdwViewStack, NOTIFY_VISIBLE_CHILD } from './adw-view-stack.js';
 export type { AdwViewStackPage, NotifyVisibleChildEventData } from './adw-view-stack.js';
 export { AdwViewSwitcherBase, NOTIFY_SELECTED as NOTIFY_VIEW_SELECTED } from './view-switcher-base.js';

package/lib/types/widgets/navigation-stack.d.ts

@@ -61,11 +61,8 @@ export declare class NsNavigationStack {
     private readonly _onDiagnostic;
     private _pending;
     constructor(host: NsNavigationHost, options?: NsNavigationStackOptions);
-    /** The currently-visible page view, or `null`. */
     get visiblePage(): View | null;
-    /** The currently-visible page tag, or `null`. */
     get visiblePageTag(): string | null;
-    /** The current navigation stack depth. */
     get depth(): number;
     /** The navigation stack, bottom-first. */
     get stack(): readonly View[];
@@ -79,7 +76,6 @@ export declare class NsNavigationStack {
     get animateTransitions(): boolean;
     /** `Adw.NavigationView:pop-on-escape` — consulted by {@link popFromEscape}. */
     get popOnEscape(): boolean;
-    /** Whether `view` is known to this navigation view. */
     isRegistered(view: View): boolean;
     /** `view`'s tag, or `null`. */
     tagOf(view: View): string | null;
@@ -87,7 +83,6 @@ export declare class NsNavigationStack {
     titleOf(view: View): string;
     /** Whether `view` may be popped by a shortcut or a back button. */
     canPopOf(view: View): boolean;
-    /** The page with this tag, or `null`. */
     findPage(tag: string): View | null;
     /** The page popping `view` would reveal, or `null`. */
     getPreviousPage(view: View): View | null;
@@ -104,21 +99,17 @@ export declare class NsNavigationStack {
     remove(view: View): boolean;
     /** Push a page (a previously-registered tag, or a fresh view) onto the stack. */
     push(viewOrTag: View | string, options?: AdwNavigationPageProps): boolean;
-    /** Push the page carrying `tag`. */
     pushByTag(tag: string): boolean;
     /** Pop the top page. `can-pop` does NOT gate this — it gates the shortcuts. */
     pop(): boolean;
     /** Pop until `view` is visible, in ONE transition. */
     popToPage(view: View): boolean;
-    /** Pop until the page carrying `tag` is visible. */
     popToTag(tag: string): boolean;
     /**
-     * Replace the whole stack. String entries are resolved BEFORE anything is
-     * mutated, so replacing the stack with the tag of a dynamically-pushed page
-     * keeps that page (replace_with_tags:3136-3147).
+     * Replace the whole stack. String entries are resolved BEFORE anything is mutated,
+     * so replacing the stack with the tag of a dynamically-pushed page keeps that page.
      */
     replace(entries: ReadonlyArray<View | string | null>, props?: (view: View) => AdwNavigationPageProps | undefined): void;
-    /** Replace the stack with the pages carrying `tags`. */
     replaceWithTags(tags: readonly string[]): void;
     /** Set a page's tag. Rejected when another page already owns it. */
     setTag(view: View, tag: string | null): boolean;
@@ -126,9 +117,7 @@ export declare class NsNavigationStack {
     setTitle(view: View, title: string): boolean;
     /** Set a page's `can-pop`: gates the shortcuts and a back button, not `pop()`. */
     setCanPop(view: View, canPop: boolean): boolean;
-    /** Set `animate-transitions`. */
     setAnimateTransitions(value: boolean): boolean;
-    /** Set `pop-on-escape`. */
     setPopOnEscape(value: boolean): boolean;
     /** The `can-pop`-aware pop behind a hardware back button or Alt+Left. */
     popFromShortcut(): NavigationShortcutResult;

package/lib/types/widgets/preferences-group-state.d.ts

@@ -11,9 +11,7 @@ export declare const PREFERENCES_GROUP_HEADER_CLASS = "adw-preferences-group-hea
 export declare const PREFERENCES_GROUP_SINGLE_LINE_CLASS = "single-line";
 /** What a group knows about itself when it re-derives its visuals. */
 export interface NsPreferencesGroupInput {
-    /** `AdwPreferencesGroup:title`. */
     title?: string | null;
-    /** `AdwPreferencesGroup:description`. */
     description?: string | null;
     /** Whether a `header-suffix` view is set. */
     hasHeaderSuffix?: boolean;
@@ -22,9 +20,7 @@ export interface NsPreferencesGroupInput {
 }
 /** The NativeScript form of {@link PreferencesGroupHeaderState}. */
 export interface NsPreferencesGroupVisuals {
-    /** `visibility` for the title label. */
     titleVisibility: NsVisibility;
-    /** `visibility` for the description label. */
     descriptionVisibility: NsVisibility;
     /** `visibility` for the whole header box. */
     headerVisibility: NsVisibility;
@@ -36,17 +32,15 @@ export interface NsPreferencesGroupVisuals {
 /**
  * The five derived states for a group.
  *
- * `useMarkup: false` is deliberate and is the same choice the browser renderer
- * makes: an NS `Label` shows the string verbatim (it has no Pango markup), so
- * visibility must be judged on the string that is actually painted. Rendering
- * markup is a separate, still-open gap; closing it flips this one flag.
+ * `useMarkup: false` is deliberate and matches the browser renderer: an NS `Label`
+ * shows the string verbatim (no Pango markup), so visibility must be judged on the
+ * string that is actually painted. Rendering markup is a still-open gap; closing it
+ * flips this one flag.
  */
 export declare function preferencesGroupHeaderState(input: NsPreferencesGroupInput): PreferencesGroupHeaderState;
 /**
- * `visibility` / `className` a group must apply for the given inputs.
- *
- * `'collapse'` rather than `'hidden'`: a hidden NS view still occupies its
- * space, which would leave the header's padding behind on a group that has no
- * header — the very thing `update_header_visibility` exists to avoid.
+ * `visibility` / `className` a group must apply for the given inputs. `'collapse'`
+ * rather than `'hidden'`: a hidden NS view still occupies its space, which would leave
+ * the header's padding behind on a group that has no header.
  */
 export declare function preferencesGroupVisuals(input: NsPreferencesGroupInput): NsPreferencesGroupVisuals;

package/lib/types/widgets/preferences-search.d.ts

@@ -2,11 +2,11 @@ import type { PreferencesSearchPage, PreferencesSearchResult, SearchPreferencesO
 /**
  * What the search reads off a row widget.
  *
- * `isActionRow` is a declared property rather than an `instanceof` test,
- * because the NativeScript hierarchy does NOT match the GObject one:
- * `AdwEntryRow extends AdwActionRow` here so it can reuse the row chrome, while
- * in C it derives from `AdwPreferencesRow` (adw-entry-row.c:90) and its text is
- * therefore deliberately NOT searchable. The row classes carry the C answer.
+ * `isActionRow` is a declared property rather than an `instanceof` test, because the
+ * NativeScript hierarchy does NOT match the GObject one: `AdwEntryRow extends
+ * AdwActionRow` here to reuse the row chrome, while in C it derives from
+ * `AdwPreferencesRow` and its text is therefore deliberately NOT searchable. The row
+ * classes carry the C answer.
  */
 export interface NsSearchableRow {
     /** `AdwPreferencesRow:title`. */

package/lib/types/widgets/row-state.d.ts

@@ -6,22 +6,16 @@ export type { AdwRowLabels, ButtonRowRenderState };
 /** The two `View.visibility` values an Adwaita row ever assigns. */
 export type NsVisibility = 'visible' | 'collapse';
 /**
- * `visibility` for a shown/hidden view.
- *
- * `'collapse'` rather than `'hidden'`: a hidden NS view still occupies its
- * space, so an empty subtitle would leave its whole line behind — which is the
- * one thing the binding exists to prevent.
+ * `visibility` for a shown/hidden view. `'collapse'` rather than `'hidden'`: a hidden
+ * NS view still occupies its space, so an empty subtitle would leave its whole line
+ * behind — the one thing the binding exists to prevent.
  */
 export declare function nsVisibility(shown: boolean): NsVisibility;
 /** The NativeScript form of a title/subtitle label pair. */
 export interface NsRowLabelVisuals {
-    /** Text for the title `Label`. */
     title: string;
-    /** `visibility` for the title `Label`. */
     titleVisibility: NsVisibility;
-    /** Text for the subtitle `Label`. */
     subtitle: string;
-    /** `visibility` for the subtitle `Label`. */
     subtitleVisibility: NsVisibility;
 }
 /** What a row must apply to its two labels for the given title/subtitle. */
@@ -30,42 +24,32 @@ export declare function rowLabelVisuals(input: AdwRowLabelInput): NsRowLabelVisu
 export declare function toLabelVisuals(labels: AdwRowLabels): NsRowLabelVisuals;
 /** The NativeScript form of an `Adw.ButtonRow`'s two icons. */
 export interface NsButtonRowIconVisuals {
-    /** Payload for the leading icon. */
     startIcon: string;
-    /** `visibility` for the leading icon. */
     startIconVisibility: NsVisibility;
-    /** Payload for the trailing icon. */
     endIcon: string;
-    /** `visibility` for the trailing icon. */
     endIconVisibility: NsVisibility;
 }
 /**
  * What a button row must apply to its two icons.
  *
- * The TITLE half of `ButtonRowRenderState` is deliberately not mapped here: the
- * NativeScript button row reuses the action row's title `Label` and therefore
- * its title state, so routing the title through a second state object would give
- * one label two sources of truth — the exact shape this package exists to
- * remove. {@link rowLabelVisuals} paints it.
+ * The TITLE half of `ButtonRowRenderState` is deliberately not mapped here: the NS
+ * button row reuses the action row's title `Label` and its title state, so routing the
+ * title through a second state object would give one label two sources of truth.
+ * {@link rowLabelVisuals} paints it.
  *
- * NOTE ON THE ICON PAYLOAD: GTK stores an icon NAME and resolves it through the
- * icon theme; this port stores the symbolic SVG source itself, because `AdwIcon`
- * renders SVG rather than looking a name up. `ButtonRowState` is indifferent —
- * the rule it applies is `string_is_not_empty`, which reads the first byte and
- * does not care what the string means.
+ * The icon payload is the symbolic SVG SOURCE, not GTK's icon name, because `AdwIcon`
+ * renders SVG rather than resolving a name. `ButtonRowState` is indifferent: its rule
+ * is `string_is_not_empty`, which reads the first byte.
  */
 export declare function buttonRowIconVisuals(state: ButtonRowRenderState): NsButtonRowIconVisuals;
 /**
- * Whether a view is "sensitive" in the sense the `activatable-widget` binding
- * reads (`GtkWidget:sensitive` → `GtkListBoxRow:activatable`,
- * adw-action-row.c:729-732).
+ * Whether a view is "sensitive" in the sense the `activatable-widget` binding reads
+ * (`GtkWidget:sensitive` → `GtkListBoxRow:activatable`).
  *
- * NativeScript has no `sensitive`; `isUserInteractionEnabled` is the nearest
- * flag it surfaces (its own docs map it to `gtk_widget_set_can_target`). The two
- * are not identical in GTK — an insensitive widget is also greyed out, a
- * can't-target one is not — but `isUserInteractionEnabled` is the only property
- * a NativeScript view has for "the user cannot operate this", so it is what the
- * binding reads here. A view that has never been touched reports `true`, which
- * is also GTK's default.
+ * NativeScript has no `sensitive`; `isUserInteractionEnabled` is the nearest flag it
+ * surfaces (its own docs map it to `gtk_widget_set_can_target`). The two differ in GTK
+ * — an insensitive widget is also greyed out, a can't-target one is not — but it is the
+ * only property NS has for "the user cannot operate this". An untouched view reports
+ * `true`, which is also GTK's default.
  */
 export declare function isViewSensitive(view: Pick<View, 'isUserInteractionEnabled'> | null | undefined): boolean;

package/lib/types/widgets/shortcut-label.d.ts

@@ -0,0 +1,54 @@
+import type { ShortcutLabelOptions } from '@gjsify/adwaita-core';
+/** The host `StackLayout`'s own class. */
+export declare const SHORTCUT_LABEL_CLASS = "adw-shortcut-label";
+/** One combination — the keycaps of a single accelerator, drawn side by side. */
+export declare const SHORTCUT_LABEL_KEYS_CLASS = "adw-shortcut-label-keys";
+/** One keycap. libadwaita's own name, so the theme rule reads like the SCSS. */
+export declare const SHORTCUT_LABEL_KEYCAP_CLASS = "keycap";
+/** The text inside a keycap — the Label a `<span>`'s text node stands in for. */
+export declare const SHORTCUT_LABEL_CAP_TEXT_CLASS = "adw-shortcut-label-cap-text";
+/** The `L`/`R` marker of a sided modifier key, inside the cap it belongs to. */
+export declare const SHORTCUT_LABEL_SIDE_CLASS = "adw-shortcut-label-side";
+/** `dim_label` — the separators, and the half the placeholder shares with them. */
+export declare const SHORTCUT_LABEL_DIMMED_CLASS = "dimmed";
+/** The disabled placeholder, so a consumer can style it without counting children. */
+export declare const SHORTCUT_LABEL_DISABLED_CLASS = "adw-shortcut-label-disabled";
+/** Carries the 6px GTK gets from `border-spacing` — every child but the first. */
+export declare const SHORTCUT_LABEL_SPACED_CLASS = "adw-shortcut-label-spaced";
+/** A node of the view tree: `box` is a horizontal `StackLayout`, `label` a `Label`. */
+export interface ShortcutLabelViewSpec {
+    readonly kind: 'box' | 'label';
+    /** The view's `className`, space-separated as NS holds it. */
+    readonly className: string;
+    /** A label's text; `''` for a box. */
+    readonly text: string;
+    /** A box's children; empty for a label. */
+    readonly children: readonly ShortcutLabelViewSpec[];
+    /** `style.direction` to pin, or `null` to inherit it. */
+    readonly direction: 'ltr' | null;
+}
+/** What the widget rebuilds itself from. */
+export interface ShortcutLabelRenderPlan {
+    /** The host's children, in visual order. */
+    readonly children: readonly ShortcutLabelViewSpec[];
+    /** The name a screen reader announces for the whole label. */
+    readonly accessibleLabel: string;
+    /** The fragment that failed to parse, or `null` — `children` is the partial result. */
+    readonly error: string | null;
+}
+/**
+ * Which modifier glyph set to draw — `#ifdef __APPLE__` upstream, and on
+ * NativeScript that is iOS. Split out so the choice is a value the suite can
+ * drive both sides of, rather than a branch reachable only on a device.
+ */
+export declare function shortcutLabelPlatform(isIos: boolean): 'default' | 'apple';
+/**
+ * The direction the sequence arrow follows.
+ *
+ * NS's `direction` is an INHERITED CSS property that resolves to `null` until
+ * the view is attached, which is exactly when a widget built in its constructor
+ * would read it — so the null case is LTR and the widget re-reads on load.
+ */
+export declare function shortcutLabelDirection(direction: 'ltr' | 'rtl' | null | undefined): 'ltr' | 'rtl';
+/** The view tree for one accelerator, with the accessible name and any parse error. */
+export declare function shortcutLabelRenderPlan(accelerator: string, options?: ShortcutLabelOptions): ShortcutLabelRenderPlan;

package/lib/types/widgets/sidebar-model.d.ts

@@ -4,15 +4,13 @@ export { SidebarState };
 export type { AdwSidebarItemSpec, AdwSidebarSectionSpec, SidebarItemFilter };
 /**
  * The section list a flat `AdwSidebar.setItems(labels)` call means: one untitled
- * section, which renders no header at all (a first + untitled section's header is
- * bound to a non-empty title, adw-sidebar.c:1521-1527).
+ * section, which renders no header at all (a section header's `visible` is bound to a
+ * non-empty title).
  */
 export declare function sidebarSectionsFromLabels(labels: readonly string[]): AdwSidebarSectionSpec[];
 /**
- * The class string one navigation row carries.
- *
- * `selectionVisible` is false in page mode, where libadwaita tracks the
- * selection but never paints it (adw-sidebar.c:2948-2951) — its rows are plain
- * boxed-list `AdwActionRow`s with no selected state.
+ * The class string one navigation row carries. `selectionVisible` is false in page
+ * mode, where libadwaita tracks the selection but never paints it — those rows are
+ * plain boxed-list `AdwActionRow`s with no selected state.
  */
 export declare function sidebarRowClassName(selected: boolean, selectionVisible: boolean): string;

package/lib/types/widgets/split-button.d.ts

@@ -3,53 +3,36 @@ export type { AdwMenuEntry, SplitButtonDirection };
 /** Text of the sheet's dismiss button. */
 export declare const MENU_CANCEL_LABEL = "Cancel";
 /**
- * The libadwaita arrow glyph names mapped to real Adwaita symbolic SVGs.
- *
- * Keyed by {@link AdwArrowIcon} and therefore TOTAL: which glyph a direction gets
- * is decided in core, and a glyph this table has no SVG for is a compile error
- * rather than a fallback arrow.
+ * The libadwaita arrow glyph names mapped to real Adwaita symbolic SVGs. Keyed by
+ * {@link AdwArrowIcon} and therefore TOTAL: which glyph a direction gets is decided in
+ * core, and a glyph with no SVG here is a compile error rather than a fallback arrow.
  */
 export declare const ARROW_SVGS: Readonly<Record<AdwArrowIcon, string>>;
 /**
- * Normalise a menu assigned from XML or app code into entries.
- *
- * A bare `string[]` is accepted because that is what `AdwSplitButton.menu` used
- * to be and what the storybook still passes; it widens to the shared
- * {@link AdwMenuEntry} without breaking a caller.
+ * Normalise a menu assigned from XML or app code into entries. A bare `string[]` is
+ * accepted (the storybook passes one) and widens to the shared {@link AdwMenuEntry}.
  */
 export declare function toMenuEntries(value: readonly (string | AdwMenuEntry)[] | null | undefined): AdwMenuEntry[];
 /**
- * The strings handed to `Dialogs.action()`, one per entry and each unique.
- *
- * A label that collides with another entry — or with the dismiss button — gets
- * zero-width spaces appended until it is distinct. Nothing changes on screen;
- * what changes is that {@link resolveMenuChoice} can now tell the entries apart.
+ * The strings handed to `Dialogs.action()`, one per entry and each unique: a label
+ * that collides with another entry — or with the dismiss button — gets zero-width
+ * spaces appended until it is distinct, so {@link resolveMenuChoice} can tell them
+ * apart.
  */
 export declare function menuSheetActions(entries: readonly AdwMenuEntry[], cancelLabel?: string): string[];
 /**
- * The position the user chose, or `-1` when the sheet was dismissed.
- *
- * Feed it the SAME array {@link menuSheetActions} produced: the strings are
- * unique there, so the lookup is a position and not a guess.
+ * The position the user chose, or `-1` when the sheet was dismissed. Feed it the SAME
+ * array {@link menuSheetActions} produced, or the lookup is a guess.
  */
 export declare function resolveMenuChoice(sheetActions: readonly string[], chosen: string | null | undefined): number;
-/**
- * The arrow SVG for a direction, keyed off the SPLIT BUTTON's glyph map — so
- * `none` is the down caret (_buttons.scss:621-623), not the hamburger this widget
- * used to render for it.
- */
+/** The arrow SVG for a direction; the split button's `none` is the down caret, not a hamburger. */
 export declare function splitButtonArrowSvg(direction: SplitButtonDirection): string;
 /**
- * Apply `AdwSplitButton.actionIcon = svg` to the content machine.
- *
- * The SVG string IS the icon identity on NativeScript (no icon theme is
- * resolved), so it goes in where GTK puts the icon NAME. Clearing it is the
- * mapping worth having in one place: C offers no "unset the icon", only the
- * side effect of filling another slot (adw-split-button.c:749-771), so an empty
- * SVG clears the content and lets the label half take over again — which is what
- * every caller assigning `actionIcon` from a nullable lookup expects.
+ * Apply `AdwSplitButton.actionIcon = svg` to the content machine. The SVG string IS
+ * the icon identity on NativeScript, so it goes where GTK puts the icon NAME.
  *
- * Lives here rather than in the widget so it is unit-testable off-device: the
- * widget module `extends GridLayout` and cannot be imported on GJS/Node.
+ * C offers no "unset the icon", only the side effect of filling another slot, so an
+ * empty SVG clears the content and lets the label half take over again — what a
+ * caller assigning `actionIcon` from a nullable lookup expects.
  */
 export declare function setActionIcon(state: SplitButtonState, svg: string | null | undefined): void;