@girs/foundryadw-1 4.2.0 → 4.4.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -5,25 +5,25 @@
5
5
  ![downloads/week](https://img.shields.io/npm/dw/@girs/foundryadw-1)
6
6
 
7
7
 
8
- GJS TypeScript type definitions for FoundryAdw-1 using [ts-for-gir](https://github.com/gjsify/ts-for-gir) v4.2.0.
8
+ GJS TypeScript type definitions for FoundryAdw-1 using [ts-for-gir](https://github.com/gjsify/ts-for-gir) v4.4.0.
9
9
 
10
10
  ## Install
11
11
 
12
- To use this type definitions, install them with NPM:
12
+ Install the type definitions with npm:
13
13
  ```bash
14
14
  npm install @girs/foundryadw-1
15
15
  ```
16
16
 
17
17
  ## Usage
18
18
 
19
- You can import this package into your project like this:
19
+ Import it like any other module:
20
20
  ```ts
21
21
  import FoundryAdw from '@girs/foundryadw-1';
22
22
  ```
23
23
 
24
24
  ### Ambient Modules
25
25
 
26
- You can also use [ambient modules](https://github.com/gjsify/ts-for-gir/tree/main/packages/cli#ambient-modules) to import this module like you would do this in JavaScript.
26
+ [Ambient modules](https://github.com/gjsify/ts-for-gir/tree/main/packages/cli#ambient-modules) let you write the same import you would in plain JavaScript.
27
27
  For this you need to include `@girs/foundryadw-1` or `@girs/foundryadw-1/ambient` in your `tsconfig` or entry point Typescript file:
28
28
 
29
29
  `index.ts`:
@@ -42,7 +42,7 @@ import '@girs/foundryadw-1'
42
42
  }
43
43
  ```
44
44
 
45
- Now you can import the ambient module with TypeScript support:
45
+ The ambient module now resolves with types:
46
46
 
47
47
  ```ts
48
48
  import FoundryAdw from 'gi://FoundryAdw?version=1';
@@ -50,7 +50,7 @@ import FoundryAdw from 'gi://FoundryAdw?version=1';
50
50
 
51
51
  ### Global import
52
52
 
53
- You can also import the module with Typescript support using the global `imports.gi` object of GJS.
53
+ GJS's global `imports.gi` works too, with types.
54
54
  For this you need to include `@girs/foundryadw-1` or `@girs/foundryadw-1/import` in your `tsconfig` or entry point Typescript file:
55
55
 
56
56
  `index.ts`:
@@ -69,7 +69,7 @@ import '@girs/foundryadw-1'
69
69
  }
70
70
  ```
71
71
 
72
- Now you have also type support for this, too:
72
+ That form carries types as well:
73
73
 
74
74
  ```ts
75
75
  const FoundryAdw = imports.gi.FoundryAdw;
@@ -77,7 +77,7 @@ const FoundryAdw = imports.gi.FoundryAdw;
77
77
 
78
78
  ### Bundle
79
79
 
80
- Depending on your project configuration, it is recommended to use a bundler like [esbuild](https://esbuild.github.io/). You can find examples using different bundlers [here](https://github.com/gjsify/ts-for-gir/tree/main/examples).
80
+ Most projects want a bundler. [esbuild](https://esbuild.github.io/) is the smallest thing that works; the [examples directory](https://github.com/gjsify/ts-for-gir/tree/main/examples) has setups for several others.
81
81
 
82
82
  ## Other packages
83
83
 
@@ -219,6 +219,23 @@ export interface Widgets {
219
219
  /** Every GType this namespace can create. A consumer derives its own tag map. */
220
220
  export type WidgetGType = keyof Widgets;
221
221
 
222
+ // ---------------------------------------------------------------------------
223
+ // Child holders — the same shape, for objects that CARRY a widget without being one.
224
+ //
225
+ // `GtkListItem`, `GtkListHeader`, `GtkColumnViewCell` and `AdwToggle` descend from
226
+ // `GObject.Object` and hold a widget through `set_child`/`get_child`. A renderer places
227
+ // them exactly like a container, so they belong in the vocabulary; a check asking "is
228
+ // this a widget" must still be able to say no. Hence a sibling table rather than four
229
+ // more rows in `Widgets`: concatenate them when you mean both.
230
+ // ---------------------------------------------------------------------------
231
+
232
+ export interface ChildHolders {
233
+
234
+ }
235
+
236
+ /** Every GType this namespace holds a child in without it being a widget. */
237
+ export type ChildHolderGType = keyof ChildHolders;
238
+
222
239
  /** The writable, optional, GObject-keyed property surface of one GType. */
223
240
  export type PropsOf<G extends WidgetGType> = Widgets[G]['props'];
224
241
 
@@ -254,6 +271,9 @@ export const OWN_SIGNALS: Readonly<Record<string, readonly string[]>>;
254
271
  /** Widget GType -> every declaration its members come from, self first. */
255
272
  export const DECLS: Readonly<Record<string, readonly string[]>>;
256
273
 
274
+ /** The GTypes in `DECLS` that hold a widget without being one — see `ChildHolders`. */
275
+ export const CHILD_HOLDERS: readonly string[];
276
+
257
277
  /** Enum GType -> the nicks this surface offers. */
258
278
  export const ENUM_NICKS: Readonly<Record<string, readonly string[]>>;
259
279
 
@@ -33,6 +33,12 @@ export const DECLS = {
33
33
  FoundryWorkspace: ['FoundryWorkspace', 'GtkWidget', 'GtkAccessible', 'GtkBuildable', 'GtkConstraintTarget'],
34
34
  };
35
35
 
36
+ // The GTypes above that are NOT widgets: they hold one through `set_child`/`get_child`
37
+ // and descend from `GObject.Object`. A renderer places them like a container; a check
38
+ // asking "is this a widget" must not count them. Derived from the accessor pair, never
39
+ // from a list — the count is in the provenance line above.
40
+ export const CHILD_HOLDERS = [];
41
+
36
42
  export const ENUM_NICKS = {
37
43
  GFileType: ['unknown', 'regular', 'directory', 'symbolic-link', 'special', 'shortcut', 'mountable'],
38
44
  };