@gjsify/adwaita-storybook 0.31.0 → 0.33.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 +3 -1
- package/package.json +5 -5
- package/src/index.ts +5 -1
- package/src/story-element.ts +2 -1
package/README.md
CHANGED
|
@@ -1,6 +1,8 @@
|
|
|
1
1
|
# @gjsify/adwaita-storybook
|
|
2
2
|
|
|
3
|
-
Browser renderer for the [`@gjsify/stories`](../../framework/stories) contract — the web counterpart of [`@gjsify/storybook`](../../framework/storybook). It renders stories as a generic Adwaita component browser built from [`@gjsify/adwaita-web`](../adwaita-web) custom elements, so a web storybook looks and behaves like the native GTK one
|
|
3
|
+
Browser renderer for the [`@gjsify/stories`](../../framework/stories) contract — the web counterpart of [`@gjsify/storybook`](../../framework/storybook). It renders stories as a generic Adwaita component browser built from [`@gjsify/adwaita-web`](../adwaita-web) custom elements, so a web storybook looks and behaves like the native GTK one.
|
|
4
|
+
|
|
5
|
+
A screenshot harness comparing the renderers is **not** implemented ([#1052](https://github.com/gjsify/gjsify/issues/1052)). The parity that is actually held is behavioural: the [`@gjsify/adwaita-core/conformance`](../adwaita-core) vector tables, which both renderer suites assert their real widgets against.
|
|
4
6
|
|
|
5
7
|
## Usage
|
|
6
8
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@gjsify/adwaita-storybook",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.33.0",
|
|
4
4
|
"description": "Browser renderer for the @gjsify/stories contract — the web counterpart of @gjsify/storybook, built on @gjsify/adwaita-web",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": "./src/index.ts",
|
|
@@ -29,12 +29,12 @@
|
|
|
29
29
|
"browser"
|
|
30
30
|
],
|
|
31
31
|
"dependencies": {
|
|
32
|
-
"@gjsify/adwaita-web": "^0.
|
|
33
|
-
"@gjsify/stories": "^0.
|
|
34
|
-
"@gjsify/storybook-core": "^0.
|
|
32
|
+
"@gjsify/adwaita-web": "^0.33.0",
|
|
33
|
+
"@gjsify/stories": "^0.33.0",
|
|
34
|
+
"@gjsify/storybook-core": "^0.33.0"
|
|
35
35
|
},
|
|
36
36
|
"devDependencies": {
|
|
37
|
-
"@gjsify/cli": "^0.
|
|
37
|
+
"@gjsify/cli": "^0.33.0",
|
|
38
38
|
"typescript": "^6.0.3"
|
|
39
39
|
},
|
|
40
40
|
"gjsify": {
|
package/src/index.ts
CHANGED
|
@@ -2,7 +2,11 @@
|
|
|
2
2
|
// The web counterpart of @gjsify/storybook: author *.web.ts files as
|
|
3
3
|
// StoryElement subclasses and render them in a generic Adwaita component browser
|
|
4
4
|
// built from @gjsify/adwaita-web, looking and behaving like the native GTK
|
|
5
|
-
// storybook
|
|
5
|
+
// storybook.
|
|
6
|
+
//
|
|
7
|
+
// A screenshot harness comparing the renderers is NOT implemented (#1052). What
|
|
8
|
+
// holds their behaviour together is the @gjsify/adwaita-core/conformance vector
|
|
9
|
+
// tables, which both renderer suites assert their real widgets against.
|
|
6
10
|
//
|
|
7
11
|
// A thin DOM adapter over @gjsify/storybook-core — the renderer-agnostic logic
|
|
8
12
|
// (story base, registry, control binding, app controller) lives in core; this
|
package/src/story-element.ts
CHANGED
|
@@ -3,7 +3,8 @@
|
|
|
3
3
|
// builds DOM with @gjsify/adwaita-web components instead of GTK widgets, but
|
|
4
4
|
// exposes the same authoring surface (getMetadata, initialize, updateArgs,
|
|
5
5
|
// teardown, addContent, meta/story/args) so a story is a near-1:1 port of its
|
|
6
|
-
// GTK twin
|
|
6
|
+
// GTK twin. That is a claim about the story SOURCE, which is readable here; that
|
|
7
|
+
// the two then render identically is not measured anywhere (#1052).
|
|
7
8
|
//
|
|
8
9
|
// Thin DOM adapter over @gjsify/storybook-core's StoryViewBase: the
|
|
9
10
|
// renderer-agnostic state (meta/story/args, onArgsChanged/setArg, the
|