@gjsify/adwaita-nativescript 0.35.0 → 0.37.0

package/lib/types/widgets/adw-action-row.d.ts

@@ -4,64 +4,49 @@ import { ActionRowState } from './row-state.js';
 export declare const ACTIVATED = "activated";
 export declare class AdwActionRow extends GridLayout {
     /**
-     * Whether libadwaita would answer `ADW_IS_ACTION_ROW` for this row — which
-     * is what decides whether the preferences SEARCH consults its subtitle
-     * (`filter_search_results`, adw-preferences-dialog.c:140-146).
+     * Whether libadwaita would answer `ADW_IS_ACTION_ROW` for this row, which decides
+     * whether the preferences SEARCH consults its subtitle.
      *
-     * A declared property, not an `instanceof` test, because this port's class
-     * tree deliberately does NOT match the GObject one: `AdwEntryRow`,
-     * `AdwExpanderRow` and `AdwButtonRow` extend this class here to reuse the
-     * row chrome, while in C all three derive from `AdwPreferencesRow`
-     * (adw-entry-row.c:90, adw-expander-row.c:72, adw-button-row.c:74). They
-     * override this to `false`, so the search behaves as GTK does.
+     * A declared property, not an `instanceof` test, because this port's class tree
+     * deliberately does NOT match the GObject one: `AdwEntryRow`, `AdwExpanderRow`
+     * and `AdwButtonRow` extend this class to reuse the row chrome, while in C all
+     * three derive from `AdwPreferencesRow`. They override this to `false`, so the
+     * search behaves as GTK does.
      */
     readonly isActionRow: boolean;
     /** The text/value column (column 1). */
     protected readonly _textStack: StackLayout;
-    /** The title label. */
     protected readonly _titleLabel: Label;
-    /** The subtitle label. */
     protected readonly _subtitleLabel: Label;
     /** The headless labels + activatable-widget coupling (ADR 0004). */
     protected readonly _rowState: ActionRowState<View>;
-    /** The currently-installed prefix view (column 0), if any. */
     private _prefix;
-    /** The currently-installed suffix view (column 2), if any. */
     private _suffix;
     constructor();
-    /**
-     * Install a prefix widget in column 0 (e.g. an `AdwIcon` symbolic icon).
-     * Replaces any previously-installed prefix. Pass `null` to clear it.
-     */
+    /** Install a prefix widget in column 0. Replaces any previous one; `null` clears. */
     setPrefix(view: View | null): void;
-    /** The currently-installed prefix view, or `null`. */
     get prefix(): View | null;
     /** The row title (column 1, top line). */
     get title(): string;
     set title(value: string);
     /**
-     * The row subtitle (column 1, dim second line). An empty subtitle collapses
-     * its label so it leaves no blank gap — `string_is_not_empty`, the same rule
-     * the title now follows.
+     * The row subtitle (column 1, dim second line). Empty collapses its label so it
+     * leaves no blank gap — `string_is_not_empty`, the rule the title follows too.
      */
     get subtitle(): string;
     set subtitle(value: string);
-    /**
-     * Install a suffix widget in column 2 (e.g. a `Switch`, `Button`, or icon).
-     * Replaces any previously-installed suffix. Pass `null` to clear it.
-     */
+    /** Install a suffix widget in column 2. Replaces any previous one; `null` clears. */
     setSuffix(view: View | null): void;
-    /** The currently-installed suffix view, or `null`. */
     get suffix(): View | null;
     /** `Adw.ActionRow:activatable-widget` — the widget this row activates. */
     get activatableWidget(): View | null;
     /**
-     * Set the activatable widget. Its sensitivity is copied into `activatable`
-     * (adw-action-row.c:729-732); clearing it LEAVES the row activatable
-     * (C:709). Call {@link syncActivatableWidgetSensitivity} when the widget's
+     * Set the activatable widget. Its sensitivity is copied into `activatable`;
+     * clearing it LEAVES the row activatable. Call
+     * {@link syncActivatableWidgetSensitivity} when the widget's
      * `isUserInteractionEnabled` changes — NativeScript has no property-change
-     * notification a plain `View` write goes through, so the live half of the
-     * binding has to be driven, not observed.
+     * notification a plain `View` write goes through, so the live half of the binding
+     * has to be driven, not observed.
      */
     set activatableWidget(widget: View | null);
     /** Re-read the activatable widget's sensitivity — the live half of the binding. */
@@ -70,24 +55,23 @@ export declare class AdwActionRow extends GridLayout {
     get activatable(): boolean;
     set activatable(value: boolean);
     /**
-     * `adw_action_row_activate` (adw-action-row.h:90): forward to the activatable
-     * widget, then emit `activated` (C:297-307). A no-op while unactivatable,
-     * because a tap on a non-activatable `GtkListBoxRow` never reaches here.
+     * `adw_action_row_activate`: forward to the activatable widget, then emit
+     * `activated`. A no-op while unactivatable, because a tap on a non-activatable
+     * `GtkListBoxRow` never reaches here.
      *
-     * FORWARDING IS SUBCLASS BUSINESS in this port. GTK sends
-     * `mnemonic-activate` and every widget knows what that means for itself;
-     * NativeScript has no such primitive on `View`, so {@link AdwSwitchRow}
-     * overrides this to toggle its slider and a plain action row only emits.
+     * FORWARDING IS SUBCLASS BUSINESS here: GTK sends `mnemonic-activate` and every
+     * widget knows what that means for itself, while NativeScript has no such
+     * primitive on `View` — so `AdwSwitchRow` overrides this to toggle its slider and
+     * a plain action row only emits.
      */
     activate(): void;
     /**
      * Whether this row's own title visibility follows `string_is_not_empty`.
      *
-     * `AdwEntryRow` sets it `false`: its two titles are the endpoints of
-     * libadwaita's empty↔filled CROSS-FADE (adw-entry-row.c:433-439), so which
-     * of them shows is decided by `emptyTarget`, not by whether the string is
-     * empty. Without the opt-out, setting a title on an entry row would reveal
-     * the small floating label on top of the large placeholder.
+     * `AdwEntryRow` sets it `false`: its two titles are the endpoints of libadwaita's
+     * empty↔filled CROSS-FADE, so which shows is decided by `emptyTarget`, not by
+     * whether the string is empty. Without the opt-out, setting a title on an entry
+     * row reveals the small floating label on top of the large placeholder.
      */
     protected _managesTitleVisibility: boolean;
     /** Push the derived label text + visibility onto the two `Label`s. */

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

@@ -6,7 +6,6 @@ export declare const ROW_ACTIVATED = "row-activated";
 export interface RowActivatedEventData extends EventData {
     /** The row's index in the `rows` array. */
     index: number;
-    /** The row object that was activated. */
     row: AdwDataGridRow;
 }
 export declare class AdwDataGrid extends GridLayout {
@@ -42,18 +41,13 @@ export declare class AdwDataGrid extends GridLayout {
      * (Re)declare the column tracks from the descriptors.
      *
      * Guarded on the derived tracks rather than run on every render: re-declaring
-     * invalidates the layout, and a data change must not move the columns. The
-     * precedent is `AdwViewSwitcherBar`, which rebuilds only when the page count
-     * moves; the key generalises that, because a column list can change without
-     * changing length (`data-grid-model.ts` says why).
+     * invalidates the layout, and a data change must not move the columns.
      */
     private _syncColumns;
     /**
-     * Rebuild the cell views when the grid's SHAPE moves, and only then.
-     *
-     * A repaint keeps the views: replacing the row under the user's finger on
-     * every data update is what the view-switcher bar's count guard exists to
-     * avoid, and here it would also drop the press state mid-touch.
+     * Rebuild the cell views when the grid's SHAPE moves, and only then — replacing
+     * the row under the user's finger on every data update would drop the press
+     * state mid-touch.
      */
     private _syncNodes;
     /** Build one row: the spanning background first, then a cell per column. */

package/lib/types/widgets/adw-entry-row.d.ts

@@ -7,15 +7,14 @@ export { EntryRowState } from '@gjsify/adwaita-core';
 export type { EntryRowRenderState, EntryRowActivation } from '@gjsify/adwaita-core';
 /** Event name emitted when {@link AdwEntryRow.text} changes. Mirrors GObject `notify::text`. */
 export declare const NOTIFY_TEXT = "notify::text";
-/** Event name emitted when the character count changes — `on_length_changed` (adw-entry-row.c:268-273). */
+/** Event name emitted when the character count changes. */
 export declare const NOTIFY_TEXT_LENGTH = "notify::text-length";
-/** Event name emitted by the apply button, or by the return key while it shows — `AdwEntryRow::apply` (C:240). */
+/** `AdwEntryRow::apply` — the apply button, or the return key while it shows. */
 export declare const SIGNAL_APPLY = "apply";
-/** Event name emitted by the return key when there is nothing to apply — `AdwEntryRow::entry-activated` (C:256). */
+/** `AdwEntryRow::entry-activated` — the return key when there is nothing to apply. */
 export declare const SIGNAL_ENTRY_ACTIVATED = "entry-activated";
 /** Payload of the `notify::text` event. */
 export interface NotifyTextEventData extends EventData {
-    /** The new text value. */
     text: string;
 }
 /** Payload of the `notify::text-length` event. */
@@ -26,15 +25,15 @@ export interface NotifyTextLengthEventData extends EventData {
 /** Payload of the `entry-activated` event. */
 export interface EntryActivatedEventData extends EventData {
     /**
-     * Whether the host must activate its default action FIRST — the C calls
-     * `gtk_widget_activate_default` on line 254 and emits the signal on line 256,
-     * and NS has no default-widget concept, so the ordering becomes the host's.
+     * Whether the host must activate its default action FIRST — C calls
+     * `gtk_widget_activate_default` before emitting, and NS has no default-widget
+     * concept, so the ordering becomes the host's.
      */
     activateDefault: boolean;
 }
 export declare class AdwEntryRow extends AdwActionRow {
-    /** `AdwEntryRow` derives from `AdwPreferencesRow` in C (adw-entry-row.c:90), so
-     *  the preferences search must NOT read the text typed into it. */
+    /** `AdwEntryRow` derives from `AdwPreferencesRow` in C, so the preferences search
+     *  must NOT read the text typed into it. */
     readonly isActionRow: boolean;
     /** The headless `update_empty` derivation + apply latch (ADR 0004). */
     protected readonly _state: EntryRowState;
@@ -48,7 +47,6 @@ export declare class AdwEntryRow extends AdwActionRow {
     protected readonly _editIcon: AdwIcon;
     /** The caps-lock warning slot (`indicator`). */
     protected readonly _indicator: AdwIcon;
-    /** The apply button. */
     protected readonly _applyButton: AdwImageButton;
     /** The suffix installed through the inherited single-slot {@link setSuffix}. */
     private _slotSuffix;
@@ -74,36 +72,29 @@ export declare class AdwEntryRow extends AdwActionRow {
     set activatesDefault(value: boolean);
     /** Whether the field currently has focus. */
     get editing(): boolean;
-    /**
-     * Append a suffix — `adw_entry_row_add_suffix` (adw-entry-row.c:885-899),
-     * which appends into a BOX so suffixes COEXIST.
-     */
+    /** Append a suffix — `adw_entry_row_add_suffix` appends into a BOX, so suffixes COEXIST. */
     addSuffix(view: View): void;
     /**
-     * The inherited single-slot API, kept working for existing consumers: it
-     * replaces only the suffix a previous `setSuffix` installed.
-     *
-     * `AdwActionRow.setSuffix` removes whatever sat in the slot, which detached
-     * the password row's own peek toggle the moment a consumer set a suffix —
-     * while `_peekButton` kept pointing at the detached view, so the row could
-     * never be revealed again. Upstream has no such conflict because there is no
-     * single slot: `add_suffix` appends.
+     * The inherited single-slot API, narrowed to replace only the suffix a previous
+     * `setSuffix` installed. `AdwActionRow.setSuffix` removes whatever sits in the
+     * slot, which would detach the password row's own peek toggle — leaving
+     * `_peekButton` pointing at a detached view, so the row could never be revealed
+     * again. Upstream has no such conflict: `add_suffix` appends.
      */
     setSuffix(view: View | null): void;
     /** The suffix installed through {@link setSuffix}, or `null`. */
     get suffix(): View | null;
     /**
-     * Drive the trailing indicator — `adw_entry_row_set_show_indicator`
-     * (adw-entry-row-private.h, C:1281-1296). Private-to-the-library upstream,
-     * public here because `AdwPasswordEntryRow` composes rather than reaching
-     * into a private header.
+     * Drive the trailing indicator — `adw_entry_row_set_show_indicator`. Private to
+     * the library upstream, public here because `AdwPasswordEntryRow` composes rather
+     * than reaching into a private header.
      */
     setShowIndicator(show: boolean): void;
-    /** `adw_entry_row_set_indicator_icon_name` (C:1263-1273), as an Adwaita symbolic SVG. */
+    /** `adw_entry_row_set_indicator_icon_name`, as an Adwaita symbolic SVG. */
     setIndicatorIcon(svg: string): void;
-    /** Apply the pending edit — the apply button tap (C:229-241). */
+    /** Apply the pending edit — the apply button tap. */
     apply(): void;
-    /** `text_activated_cb` (C:243-266) — exactly one of the two signals. */
+    /** `text_activated_cb` — exactly one of the two signals. */
     private _activate;
     /** Paint one render snapshot through the shared (spec-driven) painter. */
     protected _render(state: EntryRowRenderState): void;

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

@@ -6,38 +6,29 @@ export type { ButtonContentEllipsize };
 export declare const BUTTON_CONTENT_CAN_SHRINK_CLASS = "can-shrink";
 /**
  * The SVG the icon view is given: the app's, or the `image-missing` asset for an
- * empty slot.
+ * empty slot — the fallback `init` applies too, while `icon_name` is still `""`.
  *
- * That fallback is `gtk_image_set_from_icon_name (icon, "image-missing")`
- * (adw-button-content.c:355-356), applied by `init` too while `icon_name` is
- * still `""` (:284, :294). The widget NEVER hides the image — only the label
- * (:300, :398) — so this port keeps the icon view parented at all times and
- * swaps its source, which is the same shape as the C. The doc comments at :228
- * and :343 claim the icon is hidden instead; the code disagrees with them and
- * this follows the code (see the conformance vector's `rule`).
+ * The C NEVER hides the image, only the label, so this port keeps the icon view
+ * parented at all times and swaps its source. Upstream's own doc comments claim the
+ * icon is hidden instead; the code disagrees with them and this follows the code
+ * (see the conformance vector's `rule`).
  */
 export declare function buttonContentIconSvg(svg: string): string;
 /** Whether the icon shown is the empty-slot fallback rather than an app asset. */
 export declare function buttonContentIconIsFallback(svg: string): boolean;
 /**
- * The parent button's `className` with `image-text-button` added — the root-time
- * half of `adw_button_content_root` (:115).
- *
- * Adds rather than rewrites, so the `adw-button suggested-action pill` a caller
- * composed survives; and it is idempotent, so a re-parent cannot double the
- * token.
+ * The parent button's `className` with `image-text-button` added — the root-time half
+ * of `adw_button_content_root`. Adds rather than rewrites, so a caller's composed
+ * classes survive, and is idempotent, so a re-parent cannot double the token.
  */
 export declare function buttonContentRootedParentClassName(current: string): string;
 /**
- * The parent button's `className` with `image-text-button` removed — the unroot
- * half (:126).
- *
- * The C removes it on unroot rather than leaving it behind, so a button that
- * loses its content goes back to plain-button padding. A port that only ever
- * added the class would leave the 9px on a button that is now text-only.
+ * The parent button's `className` with `image-text-button` removed — the unroot half.
+ * A button that loses its content must go back to plain-button padding, or the 9px
+ * stays on a now text-only button.
  */
 export declare function buttonContentUnrootedParentClassName(current: string): string;
-/** The label view's `visibility` — NS's spelling of `gtk_widget_set_visible` (:398). */
+/** The label view's `visibility` — NS's spelling of `gtk_widget_set_visible`. */
 export declare function buttonContentLabelVisibility(label: string): 'visible' | 'collapse';
 /** The content's own `className` for a `can-shrink` value, other tokens untouched. */
 export declare function buttonContentClassName(current: string, canShrink: boolean): string;

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

@@ -2,10 +2,9 @@ import type { Label } from '@nativescript/core';
 import { CarouselState } from '@gjsify/adwaita-core';
 import type { CarouselScrollRequest, CarouselStateChange } from '@gjsify/adwaita-core';
 /**
- * Default page width (DIPs) used for offset math until the consumer sets
- * `pageWidth`. libadwaita MEASURES its pages (adw-carousel.c:739-765); NS gives
- * a widget no size before its first layout pass, so a plausible phone-width
- * default keeps the offsets sane until the consumer supplies the real one.
+ * Default page width (DIPs) for the offset math until the consumer sets `pageWidth`.
+ * libadwaita MEASURES its pages; NS gives a widget no size before its first layout
+ * pass, so a plausible phone width keeps the offsets sane until then.
  */
 export declare const DEFAULT_CAROUSEL_PAGE_WIDTH = 320;
 /** Construction seams an `AdwCarousel` hands to its state machine. */
@@ -18,31 +17,29 @@ export interface NsCarouselStateOptions {
 /**
  * The state machine an `AdwCarousel` delegates to.
  *
- * `animateScroll` is FALSE: the `ScrollView` animates the pixels, but it reports
- * nothing until it has, and on an untested platform it may report nothing at
- * all. Keeping the model authoritative means a `scrollToPage` is correct the
- * instant it is called, which is also what the port did before the lift —
- * {@link CarouselScrollSync} is what keeps the two from fighting.
+ * `animateScroll` is FALSE: the `ScrollView` animates the pixels but reports nothing
+ * until it has, and on an untested platform it may report nothing at all. Keeping the
+ * model authoritative makes a `scrollToPage` correct the instant it is called;
+ * {@link CarouselScrollSync} keeps the two from fighting.
  */
 export declare function createCarouselState(options?: NsCarouselStateOptions): CarouselState;
 /** A page width that can be divided by — anything else falls back to the default. */
 export declare function normalizeCarouselPageWidth(value: number): number;
-/** The horizontal scroll offset in DIPs for a position — `distance * position` (adw-carousel.c:797-801). */
+/** The horizontal scroll offset in DIPs for a position — `distance * position`. */
 export declare function carouselScrollOffset(position: number, distance: number): number;
 /** The inverse: the position a `ScrollView` at `offset` is showing. */
 export declare function carouselPositionAtOffset(offset: number, distance: number): number;
 /**
  * Keeps the model in step with a `ScrollView` that animates its own scrolls.
  *
- * Without this the two fight: the widget moves the model the moment
- * `scrollToPage` is called, then the animation replays every intermediate offset
- * back at it, so the dots would run backwards to where the scroll STARTED and
- * crawl forward again, emitting a second `page-changed` on arrival.
+ * Without this the two fight: the widget moves the model the moment `scrollToPage`
+ * is called, then the animation replays every intermediate offset back at it, so the
+ * dots run backwards to where the scroll STARTED and crawl forward again, emitting a
+ * second `page-changed` on arrival.
  *
- * So a programmatic scroll declares its destination with {@link expect}, and
- * every offset before that destination is ignored. A scroll nobody declared is a
- * user swipe and drives the model directly — which is how a free flick gets a
- * fractional position at all, something the port had no way to observe.
+ * So a programmatic scroll declares its destination with {@link expect} and every
+ * offset before it is ignored. A scroll nobody declared is a user swipe and drives the
+ * model directly — which is how a free flick gets a fractional position.
  */
 export declare class CarouselScrollSync {
     /** Position a programmatic scroll is animating towards, `null` while idle. */

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;