@cratis/scene.blueprint.components 0.1.0

package/dist/esm/gallery/GalleryScreenPreview.js

@@ -0,0 +1,62 @@
+import { jsx } from 'react/jsx-runtime';
+import { useMemo } from 'react';
+import { coreComponents, SceneElementView } from '@cratis/scene.react';
+import { cratisComponents } from '@cratis/scene.components';
+import { defaultBlueprintComponents, resolveElementComponentNames, composeScreenElement, LayoutConfigProvider, LayoutThemeProvider, defaultBlueprintThemes } from '@cratis/scene.blueprint.default';
+import { componentsBlueprintComponents } from '../componentsBlueprintComponents.js';
+import { componentsBlueprintProfile, componentsBlueprintCatalog } from './previewProfile.js';
+import { componentsGalleryScreen } from './screens.js';
+
+/**
+ * The registry a preview resolves against: `core`, `Cratis.Components`, the default blueprint, and this one.
+ *
+ * Merged by hand rather than through `mergePackageRegistries`, because reaching for this blueprint's own
+ * *bundle* here would be circular - the bundle is assembled from the gallery this file belongs to. Registry
+ * keys carry their package name, so merge order cannot cause a collision either way.
+ *
+ * Four of the profile's five packages are present. `PrimeReact` is not, which is why a `column` inside a
+ * table comes out unresolved - and it never reaches the DOM, because the table it belongs to is a
+ * placeholder until a host registers its query.
+ */ const componentsPreviewRegistry = {
+    ...coreComponents,
+    ...cratisComponents,
+    ...defaultBlueprintComponents,
+    ...componentsBlueprintComponents
+};
+/**
+ * Boots one gallery screen through the real engine.
+ *
+ * Nothing here is a preview-only path: the screen is a real `Screen`, its element tree is resolved by the
+ * real `resolveComponentName`, and it is rendered by the real `SceneElementView` against the real registry.
+ * That is the point of shipping a gallery at all - a mockup proves someone can draw an invoice list, and
+ * this proves the blueprint renders one.
+ *
+ * `LayoutConfigProvider` and `LayoutThemeProvider` are the default blueprint's, because the shell being
+ * previewed is the default blueprint's shell. This package provides Arc-bound pages to put inside it, and
+ * previewing them without the thing they were designed to sit in would prove the wrong thing.
+ */ function GalleryScreenPreview({ screenName, initialConfig, registry = componentsPreviewRegistry }) {
+    const element = useMemo(()=>{
+        const screen = componentsGalleryScreen(screenName);
+        if (!screen) {
+            throw new Error(`The gallery has no screen named '${screenName}'.`);
+        }
+        return resolveElementComponentNames(composeScreenElement(screen), componentsBlueprintProfile, componentsBlueprintCatalog);
+    }, [
+        screenName
+    ]);
+    return /*#__PURE__*/ jsx(LayoutConfigProvider, {
+        initialConfig: initialConfig,
+        storage: null,
+        children: /*#__PURE__*/ jsx(LayoutThemeProvider, {
+            themes: defaultBlueprintThemes,
+            children: /*#__PURE__*/ jsx(SceneElementView, {
+                element: element,
+                registry: registry,
+                resolveBinding: ()=>undefined
+            })
+        })
+    });
+}
+
+export { GalleryScreenPreview, componentsPreviewRegistry };
+//# sourceMappingURL=GalleryScreenPreview.js.map

package/dist/esm/gallery/GalleryScreenPreview.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"GalleryScreenPreview.js","sources":["../../../gallery/GalleryScreenPreview.tsx"],"sourcesContent":["// Copyright (c) Cratis. All rights reserved.\n// Licensed under the MIT license. See LICENSE file in the project root for full license information.\n\nimport { useMemo } from 'react';\nimport { ComponentRegistry, SceneElementView, coreComponents } from '@cratis/scene.react';\nimport { cratisComponents } from '@cratis/scene.components';\nimport { LayoutConfigProvider, LayoutConfigState, LayoutThemeProvider, composeScreenElement, defaultBlueprintComponents, defaultBlueprintThemes, resolveElementComponentNames } from '@cratis/scene.blueprint.default';\nimport { componentsBlueprintComponents } from '../componentsBlueprintComponents';\nimport { componentsBlueprintCatalog, componentsBlueprintProfile } from './previewProfile';\nimport { componentsGalleryScreen } from './screens';\n\n/**\n * The registry a preview resolves against: `core`, `Cratis.Components`, the default blueprint, and this one.\n *\n * Merged by hand rather than through `mergePackageRegistries`, because reaching for this blueprint's own\n * *bundle* here would be circular - the bundle is assembled from the gallery this file belongs to. Registry\n * keys carry their package name, so merge order cannot cause a collision either way.\n *\n * Four of the profile's five packages are present. `PrimeReact` is not, which is why a `column` inside a\n * table comes out unresolved - and it never reaches the DOM, because the table it belongs to is a\n * placeholder until a host registers its query.\n */\nexport const componentsPreviewRegistry: ComponentRegistry = {\n    ...coreComponents,\n    ...cratisComponents,\n    ...defaultBlueprintComponents,\n    ...componentsBlueprintComponents,\n};\n\nexport interface GalleryScreenPreviewProps {\n    /** The name of the gallery screen to boot. */\n    screenName: string;\n\n    /** Configuration to start from - a story pinning a layout mode, or a host restoring a session. */\n    initialConfig?: Partial<LayoutConfigState>;\n\n    /** The component registry to render against. Defaults to {@link componentsPreviewRegistry}. */\n    registry?: ComponentRegistry;\n}\n\n/**\n * Boots one gallery screen through the real engine.\n *\n * Nothing here is a preview-only path: the screen is a real `Screen`, its element tree is resolved by the\n * real `resolveComponentName`, and it is rendered by the real `SceneElementView` against the real registry.\n * That is the point of shipping a gallery at all - a mockup proves someone can draw an invoice list, and\n * this proves the blueprint renders one.\n *\n * `LayoutConfigProvider` and `LayoutThemeProvider` are the default blueprint's, because the shell being\n * previewed is the default blueprint's shell. This package provides Arc-bound pages to put inside it, and\n * previewing them without the thing they were designed to sit in would prove the wrong thing.\n */\nexport function GalleryScreenPreview({ screenName, initialConfig, registry = componentsPreviewRegistry }: GalleryScreenPreviewProps) {\n    const element = useMemo(() => {\n        const screen = componentsGalleryScreen(screenName);\n        if (!screen) {\n            throw new Error(`The gallery has no screen named '${screenName}'.`);\n        }\n\n        return resolveElementComponentNames(composeScreenElement(screen), componentsBlueprintProfile, componentsBlueprintCatalog);\n    }, [screenName]);\n\n    return (\n        <LayoutConfigProvider initialConfig={initialConfig} storage={null}>\n            <LayoutThemeProvider themes={defaultBlueprintThemes}>\n                <SceneElementView element={element} registry={registry} resolveBinding={() => undefined} />\n            </LayoutThemeProvider>\n        </LayoutConfigProvider>\n    );\n}\n"],"names":["componentsPreviewRegistry","coreComponents","cratisComponents","defaultBlueprintComponents","componentsBlueprintComponents","GalleryScreenPreview","screenName","initialConfig","registry","element","useMemo","screen","componentsGalleryScreen","Error","resolveElementComponentNames","composeScreenElement","componentsBlueprintProfile","componentsBlueprintCatalog","_jsx","LayoutConfigProvider","storage","LayoutThemeProvider","themes","defaultBlueprintThemes","SceneElementView","resolveBinding","undefined"],"mappings":";;;;;;;;;AAWA;;;;;;;;;;UAWaA,yBAAAA,GAA+C;AACxD,IAAA,GAAGC,cAAc;AACjB,IAAA,GAAGC,gBAAgB;AACnB,IAAA,GAAGC,0BAA0B;AAC7B,IAAA,GAAGC;AACP;AAaA;;;;;;;;;;;IAYO,SAASC,oBAAAA,CAAqB,EAAEC,UAAU,EAAEC,aAAa,EAAEC,QAAAA,GAAWR,yBAAyB,EAA6B,EAAA;AAC/H,IAAA,MAAMS,UAAUC,OAAAA,CAAQ,IAAA;AACpB,QAAA,MAAMC,SAASC,uBAAAA,CAAwBN,UAAAA,CAAAA;AACvC,QAAA,IAAI,CAACK,MAAAA,EAAQ;AACT,YAAA,MAAM,IAAIE,KAAAA,CAAM,CAAC,iCAAiC,EAAEP,UAAAA,CAAW,EAAE,CAAC,CAAA;AACtE,QAAA;QAEA,OAAOQ,4BAAAA,CAA6BC,oBAAAA,CAAqBJ,MAAAA,CAAAA,EAASK,0BAAAA,EAA4BC,0BAAAA,CAAAA;IAClG,CAAA,EAAG;AAACX,QAAAA;AAAW,KAAA,CAAA;AAEf,IAAA,qBACIY,GAAA,CAACC,oBAAAA,EAAAA;QAAqBZ,aAAAA,EAAeA,aAAAA;QAAea,OAAAA,EAAS,IAAA;AACzD,QAAA,QAAA,gBAAAF,GAAA,CAACG,mBAAAA,EAAAA;YAAoBC,MAAAA,EAAQC,sBAAAA;AACzB,YAAA,QAAA,gBAAAL,GAAA,CAACM,gBAAAA,EAAAA;gBAAiBf,OAAAA,EAASA,OAAAA;gBAASD,QAAAA,EAAUA,QAAAA;AAAUiB,gBAAAA,cAAAA,EAAgB,IAAMC;;;;AAI9F;;;;"}

package/dist/esm/gallery/applicationChrome.d.ts

@@ -0,0 +1,3 @@
+import { SceneElement } from '@cratis/scene.model';
+export declare function componentsApplicationChrome(activeScreen: string): Record<string, SceneElement[]>;
+//# sourceMappingURL=applicationChrome.d.ts.map

package/dist/esm/gallery/applicationChrome.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"applicationChrome.d.ts","sourceRoot":"","sources":["../../../gallery/applicationChrome.ts"],"names":[],"mappings":"AAGA,OAAO,EAAE,YAAY,EAAE,MAAM,qBAAqB,CAAC;AA4EnD,wBAAgB,2BAA2B,CAAC,YAAY,EAAE,MAAM,GAAG,MAAM,CAAC,MAAM,EAAE,YAAY,EAAE,CAAC,CA4BhG"}

package/dist/esm/gallery/applicationChrome.js

@@ -0,0 +1,135 @@
+import { SlotName, externalComponent, ComponentName, defaultBlueprintThemes } from '@cratis/scene.blueprint.default';
+import { groupOfScreen, labelOfScreen, componentsNavigationGroups, entriesInGroup } from './navigation.js';
+
+// Copyright (c) Cratis. All rights reserved.
+// Licensed under the MIT license. See LICENSE file in the project root for full license information.
+/**
+ * The application-shell chrome every gallery screen in this package shares.
+ *
+ * Every element here names a component the **default blueprint** declares - `topbar`, `sidebar`, `menu`,
+ * `breadcrumb`, `footer`, `configPanel`, `logo`, `userMenu` - and every slot is one of that blueprint's
+ * `SlotName`s. That is this package's dependency on it made concrete rather than merely declared: this
+ * blueprint contributes Arc-bound *pages*, and borrows the shell those pages live in.
+ *
+ * A blueprint that shipped its own topbar and its own sidebar would be a rival to the default one rather
+ * than a layer on it, and an application would have to choose. Since a profile activates one blueprint's
+ * layouts and both blueprints' templates, layering is what makes the two usable together at all.
+ */ /** The brand mark, shared by the topbar and the sidebar header. */ function logo(id) {
+    return externalComponent(id, ComponentName.Logo, {
+        label: 'Contoso Billing',
+        initials: 'CB',
+        targetScreen: 'DashboardPage'
+    });
+}
+/** One menu section per navigation group, each holding that group's entries. */ function menuSections(activeScreen) {
+    return componentsNavigationGroups.map((group)=>externalComponent(`menu-${group.toLowerCase()}`, ComponentName.Menu, {
+            title: group,
+            label: group
+        }, {
+            items: entriesInGroup(group).map((entry)=>navigationItem(entry.targetScreen, entry.label, entry.icon, entry.order, group, activeScreen))
+        }));
+}
+function navigationItem(targetScreen, label, icon, order, group, activeScreen) {
+    return externalComponent(`nav-${targetScreen}`, ComponentName.MenuItem, {
+        label,
+        targetScreen,
+        routeParameterBindings: {},
+        order,
+        group,
+        icon,
+        isActive: targetScreen === activeScreen
+    });
+}
+/** The configurator, offering the themes the default blueprint ships - this package ships none of its own. */ function configPanel() {
+    return externalComponent(ComponentName.ConfigPanel, ComponentName.ConfigPanel, {
+        title: 'Settings',
+        themes: defaultBlueprintThemes.map((theme)=>({
+                name: theme.name,
+                label: theme.name,
+                isDark: theme.isDark ?? false
+            }))
+    });
+}
+/**
+ * The trail above a screen's content, derived from the navigation rather than declared a second time.
+ *
+ * A hand-written table of breadcrumbs per screen is a second statement of where each screen sits, and the
+ * two drift the first time a screen is renamed. The navigation already knows the group and the label, so
+ * the trail follows from it.
+ */ function breadcrumbEntries(activeScreen) {
+    const group = groupOfScreen(activeScreen);
+    const label = labelOfScreen(activeScreen) ?? activeScreen;
+    return group === undefined ? [
+        {
+            label
+        }
+    ] : [
+        {
+            label: group,
+            targetScreen: 'DashboardPage'
+        },
+        {
+            label
+        }
+    ];
+}
+/**
+ * The application shell's slot content for one screen.
+ *
+ * Only the breadcrumb and which menu entry is marked active differ from screen to screen - everything else
+ * is identical, which is what chrome is for.
+ *
+ * @param activeScreen The screen being rendered, so its menu entry is marked current and its trail is built.
+ * @returns Slot content keyed by the {@link SlotName}s the default blueprint's `AppShell` layout declares.
+ */ function componentsApplicationChrome(activeScreen) {
+    return {
+        [SlotName.Topbar]: [
+            externalComponent('topbar', ComponentName.Topbar, {}, {
+                logo: [
+                    logo('topbar-logo')
+                ],
+                end: [
+                    externalComponent('topbar-user', ComponentName.UserMenu, {
+                        name: 'Amelia Nyquist',
+                        role: 'Billing owner',
+                        initials: 'AN',
+                        items: [
+                            {
+                                label: 'Invoice document',
+                                icon: 'pi pi-file-edit',
+                                targetScreen: 'ObjectEditorPage'
+                            }
+                        ]
+                    })
+                ]
+            })
+        ],
+        [SlotName.Sidebar]: [
+            externalComponent('sidebar', ComponentName.Sidebar, {
+                title: 'Contoso Billing'
+            }, {
+                logo: [
+                    logo('sidebar-logo')
+                ]
+            })
+        ],
+        [SlotName.Menu]: menuSections(activeScreen),
+        [SlotName.Breadcrumb]: [
+            externalComponent('breadcrumb', ComponentName.Breadcrumb, {
+                homeTargetScreen: 'DashboardPage',
+                items: breadcrumbEntries(activeScreen)
+            })
+        ],
+        [SlotName.Footer]: [
+            externalComponent('footer', ComponentName.Footer, {
+                text: '© Contoso · Arc-bound pages from Cratis Scene'
+            })
+        ],
+        [SlotName.ConfigPanel]: [
+            configPanel()
+        ]
+    };
+}
+
+export { componentsApplicationChrome };
+//# sourceMappingURL=applicationChrome.js.map

package/dist/esm/gallery/applicationChrome.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"applicationChrome.js","sources":["../../../gallery/applicationChrome.ts"],"sourcesContent":["// Copyright (c) Cratis. All rights reserved.\n// Licensed under the MIT license. See LICENSE file in the project root for full license information.\n\nimport { SceneElement } from '@cratis/scene.model';\nimport { ComponentName as DefaultComponentName, SlotName, defaultBlueprintThemes, externalComponent } from '@cratis/scene.blueprint.default';\nimport { componentsNavigationGroups, entriesInGroup, groupOfScreen, labelOfScreen } from './navigation';\n\n/**\n * The application-shell chrome every gallery screen in this package shares.\n *\n * Every element here names a component the **default blueprint** declares - `topbar`, `sidebar`, `menu`,\n * `breadcrumb`, `footer`, `configPanel`, `logo`, `userMenu` - and every slot is one of that blueprint's\n * `SlotName`s. That is this package's dependency on it made concrete rather than merely declared: this\n * blueprint contributes Arc-bound *pages*, and borrows the shell those pages live in.\n *\n * A blueprint that shipped its own topbar and its own sidebar would be a rival to the default one rather\n * than a layer on it, and an application would have to choose. Since a profile activates one blueprint's\n * layouts and both blueprints' templates, layering is what makes the two usable together at all.\n */\n\n/** The brand mark, shared by the topbar and the sidebar header. */\nfunction logo(id: string): SceneElement {\n    return externalComponent(id, DefaultComponentName.Logo, { label: 'Contoso Billing', initials: 'CB', targetScreen: 'DashboardPage' });\n}\n\n/** One menu section per navigation group, each holding that group's entries. */\nfunction menuSections(activeScreen: string): SceneElement[] {\n    return componentsNavigationGroups.map(group =>\n        externalComponent(\n            `menu-${group.toLowerCase()}`,\n            DefaultComponentName.Menu,\n            { title: group, label: group },\n            { items: entriesInGroup(group).map(entry => navigationItem(entry.targetScreen, entry.label, entry.icon, entry.order, group, activeScreen)) },\n        ),\n    );\n}\n\nfunction navigationItem(targetScreen: string, label: string, icon: string, order: number, group: string, activeScreen: string): SceneElement {\n    return externalComponent(`nav-${targetScreen}`, DefaultComponentName.MenuItem, {\n        label,\n        targetScreen,\n        routeParameterBindings: {},\n        order,\n        group,\n        icon,\n        isActive: targetScreen === activeScreen,\n    });\n}\n\n/** The configurator, offering the themes the default blueprint ships - this package ships none of its own. */\nfunction configPanel(): SceneElement {\n    return externalComponent(DefaultComponentName.ConfigPanel, DefaultComponentName.ConfigPanel, {\n        title: 'Settings',\n        themes: defaultBlueprintThemes.map(theme => ({ name: theme.name, label: theme.name, isDark: theme.isDark ?? false })),\n    });\n}\n\n/**\n * The trail above a screen's content, derived from the navigation rather than declared a second time.\n *\n * A hand-written table of breadcrumbs per screen is a second statement of where each screen sits, and the\n * two drift the first time a screen is renamed. The navigation already knows the group and the label, so\n * the trail follows from it.\n */\nfunction breadcrumbEntries(activeScreen: string): { label: string; targetScreen?: string }[] {\n    const group = groupOfScreen(activeScreen);\n    const label = labelOfScreen(activeScreen) ?? activeScreen;\n    return group === undefined ? [{ label }] : [{ label: group, targetScreen: 'DashboardPage' }, { label }];\n}\n\n/**\n * The application shell's slot content for one screen.\n *\n * Only the breadcrumb and which menu entry is marked active differ from screen to screen - everything else\n * is identical, which is what chrome is for.\n *\n * @param activeScreen The screen being rendered, so its menu entry is marked current and its trail is built.\n * @returns Slot content keyed by the {@link SlotName}s the default blueprint's `AppShell` layout declares.\n */\nexport function componentsApplicationChrome(activeScreen: string): Record<string, SceneElement[]> {\n    return {\n        [SlotName.Topbar]: [\n            externalComponent(\n                'topbar',\n                DefaultComponentName.Topbar,\n                {},\n                {\n                    logo: [logo('topbar-logo')],\n                    end: [\n                        externalComponent('topbar-user', DefaultComponentName.UserMenu, {\n                            name: 'Amelia Nyquist',\n                            role: 'Billing owner',\n                            initials: 'AN',\n                            items: [{ label: 'Invoice document', icon: 'pi pi-file-edit', targetScreen: 'ObjectEditorPage' }],\n                        }),\n                    ],\n                },\n            ),\n        ],\n        [SlotName.Sidebar]: [externalComponent('sidebar', DefaultComponentName.Sidebar, { title: 'Contoso Billing' }, { logo: [logo('sidebar-logo')] })],\n        [SlotName.Menu]: menuSections(activeScreen),\n        [SlotName.Breadcrumb]: [\n            externalComponent('breadcrumb', DefaultComponentName.Breadcrumb, { homeTargetScreen: 'DashboardPage', items: breadcrumbEntries(activeScreen) }),\n        ],\n        [SlotName.Footer]: [externalComponent('footer', DefaultComponentName.Footer, { text: '© Contoso · Arc-bound pages from Cratis Scene' })],\n        [SlotName.ConfigPanel]: [configPanel()],\n    };\n}\n"],"names":["logo","id","externalComponent","DefaultComponentName","Logo","label","initials","targetScreen","menuSections","activeScreen","componentsNavigationGroups","map","group","toLowerCase","Menu","title","items","entriesInGroup","entry","navigationItem","icon","order","MenuItem","routeParameterBindings","isActive","configPanel","ConfigPanel","themes","defaultBlueprintThemes","theme","name","isDark","breadcrumbEntries","groupOfScreen","labelOfScreen","undefined","componentsApplicationChrome","SlotName","Topbar","end","UserMenu","role","Sidebar","Breadcrumb","homeTargetScreen","Footer","text"],"mappings":";;;AAAA;AACA;AAMA;;;;;;;;;;;AAWC,wEAGD,SAASA,IAAAA,CAAKC,EAAU,EAAA;AACpB,IAAA,OAAOC,iBAAAA,CAAkBD,EAAAA,EAAIE,aAAAA,CAAqBC,IAAI,EAAE;QAAEC,KAAAA,EAAO,iBAAA;QAAmBC,QAAAA,EAAU,IAAA;QAAMC,YAAAA,EAAc;AAAgB,KAAA,CAAA;AACtI;AAEA,iFACA,SAASC,YAAAA,CAAaC,YAAoB,EAAA;AACtC,IAAA,OAAOC,0BAAAA,CAA2BC,GAAG,CAACC,CAAAA,QAClCV,iBAAAA,CACI,CAAC,KAAK,EAAEU,MAAMC,WAAW,EAAA,CAAA,CAAI,EAC7BV,aAAAA,CAAqBW,IAAI,EACzB;YAAEC,KAAAA,EAAOH,KAAAA;YAAOP,KAAAA,EAAOO;SAAM,EAC7B;AAAEI,YAAAA,KAAAA,EAAOC,eAAeL,KAAAA,CAAAA,CAAOD,GAAG,CAACO,CAAAA,KAAAA,GAASC,eAAeD,KAAAA,CAAMX,YAAY,EAAEW,KAAAA,CAAMb,KAAK,EAAEa,KAAAA,CAAME,IAAI,EAAEF,KAAAA,CAAMG,KAAK,EAAET,KAAAA,EAAOH,YAAAA,CAAAA;AAAe,SAAA,CAAA,CAAA;AAGvJ;AAEA,SAASU,cAAAA,CAAeZ,YAAoB,EAAEF,KAAa,EAAEe,IAAY,EAAEC,KAAa,EAAET,KAAa,EAAEH,YAAoB,EAAA;IACzH,OAAOP,iBAAAA,CAAkB,CAAC,IAAI,EAAEK,cAAc,EAAEJ,aAAAA,CAAqBmB,QAAQ,EAAE;AAC3EjB,QAAAA,KAAAA;AACAE,QAAAA,YAAAA;AACAgB,QAAAA,sBAAAA,EAAwB,EAAC;AACzBF,QAAAA,KAAAA;AACAT,QAAAA,KAAAA;AACAQ,QAAAA,IAAAA;AACAI,QAAAA,QAAAA,EAAUjB,YAAAA,KAAiBE;AAC/B,KAAA,CAAA;AACJ;AAEA,+GACA,SAASgB,WAAAA,GAAAA;AACL,IAAA,OAAOvB,kBAAkBC,aAAAA,CAAqBuB,WAAW,EAAEvB,aAAAA,CAAqBuB,WAAW,EAAE;QACzFX,KAAAA,EAAO,UAAA;AACPY,QAAAA,MAAAA,EAAQC,sBAAAA,CAAuBjB,GAAG,CAACkB,CAAAA,SAAU;AAAEC,gBAAAA,IAAAA,EAAMD,MAAMC,IAAI;AAAEzB,gBAAAA,KAAAA,EAAOwB,MAAMC,IAAI;gBAAEC,MAAAA,EAAQF,KAAAA,CAAME,MAAM,IAAI;aAAM,CAAA;AACtH,KAAA,CAAA;AACJ;AAEA;;;;;;IAOA,SAASC,kBAAkBvB,YAAoB,EAAA;AAC3C,IAAA,MAAMG,QAAQqB,aAAAA,CAAcxB,YAAAA,CAAAA;IAC5B,MAAMJ,KAAAA,GAAQ6B,cAAczB,YAAAA,CAAAA,IAAiBA,YAAAA;AAC7C,IAAA,OAAOG,UAAUuB,SAAAA,GAAY;AAAC,QAAA;AAAE9B,YAAAA;AAAM;KAAE,GAAG;AAAC,QAAA;YAAEA,KAAAA,EAAOO,KAAAA;YAAOL,YAAAA,EAAc;AAAgB,SAAA;AAAG,QAAA;AAAEF,YAAAA;AAAM;AAAE,KAAA;AAC3G;AAEA;;;;;;;;IASO,SAAS+B,2BAAAA,CAA4B3B,YAAoB,EAAA;IAC5D,OAAO;QACH,CAAC4B,QAAAA,CAASC,MAAM,GAAG;AACfpC,YAAAA,iBAAAA,CACI,QAAA,EACAC,aAAAA,CAAqBmC,MAAM,EAC3B,EAAC,EACD;gBACItC,IAAAA,EAAM;oBAACA,IAAAA,CAAK,aAAA;AAAe,iBAAA;gBAC3BuC,GAAAA,EAAK;oBACDrC,iBAAAA,CAAkB,aAAA,EAAeC,aAAAA,CAAqBqC,QAAQ,EAAE;wBAC5DV,IAAAA,EAAM,gBAAA;wBACNW,IAAAA,EAAM,eAAA;wBACNnC,QAAAA,EAAU,IAAA;wBACVU,KAAAA,EAAO;AAAC,4BAAA;gCAAEX,KAAAA,EAAO,kBAAA;gCAAoBe,IAAAA,EAAM,iBAAA;gCAAmBb,YAAAA,EAAc;AAAmB;AAAE;AACrG,qBAAA;AACH;AACL,aAAA;AAEP,SAAA;QACD,CAAC8B,QAAAA,CAASK,OAAO,GAAG;YAACxC,iBAAAA,CAAkB,SAAA,EAAWC,aAAAA,CAAqBuC,OAAO,EAAE;gBAAE3B,KAAAA,EAAO;aAAkB,EAAG;gBAAEf,IAAAA,EAAM;oBAACA,IAAAA,CAAK,cAAA;AAAgB;AAAC,aAAA;AAAG,SAAA;AAChJ,QAAA,CAACqC,QAAAA,CAASvB,IAAI,GAAGN,YAAAA,CAAaC,YAAAA,CAAAA;QAC9B,CAAC4B,QAAAA,CAASM,UAAU,GAAG;YACnBzC,iBAAAA,CAAkB,YAAA,EAAcC,aAAAA,CAAqBwC,UAAU,EAAE;gBAAEC,gBAAAA,EAAkB,eAAA;AAAiB5B,gBAAAA,KAAAA,EAAOgB,iBAAAA,CAAkBvB,YAAAA;AAAc,aAAA;AAChJ,SAAA;QACD,CAAC4B,QAAAA,CAASQ,MAAM,GAAG;YAAC3C,iBAAAA,CAAkB,QAAA,EAAUC,aAAAA,CAAqB0C,MAAM,EAAE;gBAAEC,IAAAA,EAAM;AAAgD,aAAA;AAAG,SAAA;QACxI,CAACT,QAAAA,CAASX,WAAW,GAAG;AAACD,YAAAA,WAAAA;AAAc;AAC3C,KAAA;AACJ;;;;"}

package/dist/esm/gallery/index.d.ts

@@ -0,0 +1,7 @@
+export * from './navigation';
+export * from './applicationChrome';
+export * from './screens';
+export * from './previewProfile';
+export * from './GalleryScreenPreview';
+export * from './DialogTemplatePreview';
+//# sourceMappingURL=index.d.ts.map

package/dist/esm/gallery/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../gallery/index.ts"],"names":[],"mappings":"AAGA,cAAc,cAAc,CAAC;AAC7B,cAAc,qBAAqB,CAAC;AACpC,cAAc,WAAW,CAAC;AAC1B,cAAc,kBAAkB,CAAC;AACjC,cAAc,wBAAwB,CAAC;AACvC,cAAc,yBAAyB,CAAC"}

package/dist/esm/gallery/index.js

@@ -0,0 +1,7 @@
+export * from './navigation';
+export * from './applicationChrome';
+export * from './screens';
+export * from './previewProfile';
+export * from './GalleryScreenPreview';
+export * from './DialogTemplatePreview';
+//# sourceMappingURL=index.js.map

package/dist/esm/gallery/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../gallery/index.ts"],"names":[],"mappings":"AAGA,cAAc,cAAc,CAAC;AAC7B,cAAc,qBAAqB,CAAC;AACpC,cAAc,WAAW,CAAC;AAC1B,cAAc,kBAAkB,CAAC;AACjC,cAAc,wBAAwB,CAAC;AACvC,cAAc,yBAAyB,CAAC"}

package/dist/esm/gallery/navigation.d.ts

@@ -0,0 +1,9 @@
+import { Contribution } from '@cratis/scene.model';
+import { NavigationEntry } from '@cratis/scene.blueprint.default';
+export declare const componentsNavigationEntries: NavigationEntry[];
+export declare const componentsNavigationContributions: Contribution[];
+export declare function entriesInGroup(group: string): NavigationEntry[];
+export declare const componentsNavigationGroups: string[];
+export declare function groupOfScreen(screenName: string): string | undefined;
+export declare function labelOfScreen(screenName: string): string | undefined;
+//# sourceMappingURL=navigation.d.ts.map

package/dist/esm/gallery/navigation.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"navigation.d.ts","sourceRoot":"","sources":["../../../gallery/navigation.ts"],"names":[],"mappings":"AAGA,OAAO,EAAE,YAAY,EAAE,MAAM,qBAAqB,CAAC;AACnD,OAAO,EAAE,eAAe,EAAkD,MAAM,iCAAiC,CAAC;AAelH,eAAO,MAAM,2BAA2B,EAAE,eAAe,EAYxD,CAAC;AASF,eAAO,MAAM,iCAAiC,EAAE,YAAY,EAIzD,CAAC;AAGJ,wBAAgB,cAAc,CAAC,KAAK,EAAE,MAAM,GAAG,eAAe,EAAE,CAE/D;AAGD,eAAO,MAAM,0BAA0B,EAAE,MAAM,EAAwE,CAAC;AAGxH,wBAAgB,aAAa,CAAC,UAAU,EAAE,MAAM,GAAG,MAAM,GAAG,SAAS,CAEpE;AAGD,wBAAgB,aAAa,CAAC,UAAU,EAAE,MAAM,GAAG,MAAM,GAAG,SAAS,CAEpE"}

package/dist/esm/gallery/navigation.js

@@ -0,0 +1,121 @@
+import { navigationContributionPoint, navigationElement } from '@cratis/scene.blueprint.default';
+
+// Copyright (c) Cratis. All rights reserved.
+// Licensed under the MIT license. See LICENSE file in the project root for full license information.
+/**
+ * The navigation for this blueprint's gallery, declared once.
+ *
+ * One list, two consumers: the sidebar menu renders it as `menuItem` elements, and the same elements go to
+ * the `Navigation` contribution point where the default blueprint's aggregation turns them back into
+ * navigation items. Maintaining a menu *and* a separate navigation declaration would mean two lists that
+ * agree right up until someone adds a screen to one of them.
+ *
+ * `navigationElement` and the contribution point name are the default blueprint's, not this package's.
+ * Reimplementing them here would produce a menu that looked identical and contributed to a contribution
+ * point nothing reads - which is the exact failure mode a blueprint-on-blueprint dependency exists to
+ * avoid.
+ */ const componentsNavigationEntries = [
+    {
+        label: 'Dashboard',
+        targetScreen: 'DashboardPage',
+        icon: 'pi pi-chart-bar',
+        group: 'Billing',
+        order: 10
+    },
+    {
+        label: 'Invoices',
+        targetScreen: 'DataListPage',
+        icon: 'pi pi-list',
+        group: 'Billing',
+        order: 20
+    },
+    {
+        label: 'In flight',
+        targetScreen: 'ObservableDataListPage',
+        icon: 'pi pi-bolt',
+        group: 'Billing',
+        order: 30
+    },
+    {
+        label: 'Invoices and detail',
+        targetScreen: 'DataListWithDetailPage',
+        icon: 'pi pi-window-maximize',
+        group: 'Billing',
+        order: 40
+    },
+    {
+        label: 'Master and detail',
+        targetScreen: 'MasterDetailPage',
+        icon: 'pi pi-table',
+        group: 'Billing',
+        order: 50
+    },
+    {
+        label: 'Register an invoice',
+        targetScreen: 'CommandFormPage',
+        icon: 'pi pi-plus-circle',
+        group: 'Billing',
+        order: 60
+    },
+    {
+        label: 'Event type schema',
+        targetScreen: 'SchemaEditorPage',
+        icon: 'pi pi-sitemap',
+        group: 'Inspect',
+        order: 10
+    },
+    {
+        label: 'Invoice document',
+        targetScreen: 'ObjectEditorPage',
+        icon: 'pi pi-file-edit',
+        group: 'Inspect',
+        order: 20
+    },
+    {
+        label: 'Billing module',
+        targetScreen: 'DataModulePage',
+        icon: 'pi pi-th-large',
+        group: 'Nesting',
+        order: 10
+    },
+    {
+        label: 'Adjustments feature',
+        targetScreen: 'DataFeatureSection',
+        icon: 'pi pi-folder',
+        group: 'Nesting',
+        order: 20
+    },
+    {
+        label: 'Record an adjustment',
+        targetScreen: 'CommandSliceSection',
+        icon: 'pi pi-pencil',
+        group: 'Nesting',
+        order: 30
+    }
+];
+/**
+ * The navigation as contributions to the `Navigation` contribution point.
+ *
+ * A screen carries these in its `contributions`, and anything bound to the contribution point recomputes
+ * from whatever is currently in scope - so a screen that contributes an extra entry gets it into the
+ * navigation without the navigation knowing that screen exists.
+ */ const componentsNavigationContributions = componentsNavigationEntries.map((entry)=>({
+        contributionPointName: navigationContributionPoint,
+        content: navigationElement(entry),
+        order: entry.order
+    }));
+/** The navigation entries of one group, in order. */ function entriesInGroup(group) {
+    return componentsNavigationEntries.filter((entry)=>entry.group === group).sort((first, second)=>first.order - second.order);
+}
+/** Every group named by the navigation, in first-declared order. */ const componentsNavigationGroups = [
+    ...new Set(componentsNavigationEntries.map((entry)=>entry.group))
+];
+/** The section a screen belongs to, for the first entry of its breadcrumb trail. */ function groupOfScreen(screenName) {
+    return componentsNavigationEntries.find((entry)=>entry.targetScreen === screenName)?.group;
+}
+/** The navigation label of a screen, for the last entry of its breadcrumb trail. */ function labelOfScreen(screenName) {
+    return componentsNavigationEntries.find((entry)=>entry.targetScreen === screenName)?.label;
+}
+
+export { componentsNavigationContributions, componentsNavigationEntries, componentsNavigationGroups, entriesInGroup, groupOfScreen, labelOfScreen };
+//# sourceMappingURL=navigation.js.map

package/dist/esm/gallery/navigation.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"navigation.js","sources":["../../../gallery/navigation.ts"],"sourcesContent":["// Copyright (c) Cratis. All rights reserved.\n// Licensed under the MIT license. See LICENSE file in the project root for full license information.\n\nimport { Contribution } from '@cratis/scene.model';\nimport { NavigationEntry, navigationContributionPoint, navigationElement } from '@cratis/scene.blueprint.default';\n\n/**\n * The navigation for this blueprint's gallery, declared once.\n *\n * One list, two consumers: the sidebar menu renders it as `menuItem` elements, and the same elements go to\n * the `Navigation` contribution point where the default blueprint's aggregation turns them back into\n * navigation items. Maintaining a menu *and* a separate navigation declaration would mean two lists that\n * agree right up until someone adds a screen to one of them.\n *\n * `navigationElement` and the contribution point name are the default blueprint's, not this package's.\n * Reimplementing them here would produce a menu that looked identical and contributed to a contribution\n * point nothing reads - which is the exact failure mode a blueprint-on-blueprint dependency exists to\n * avoid.\n */\nexport const componentsNavigationEntries: NavigationEntry[] = [\n    { label: 'Dashboard', targetScreen: 'DashboardPage', icon: 'pi pi-chart-bar', group: 'Billing', order: 10 },\n    { label: 'Invoices', targetScreen: 'DataListPage', icon: 'pi pi-list', group: 'Billing', order: 20 },\n    { label: 'In flight', targetScreen: 'ObservableDataListPage', icon: 'pi pi-bolt', group: 'Billing', order: 30 },\n    { label: 'Invoices and detail', targetScreen: 'DataListWithDetailPage', icon: 'pi pi-window-maximize', group: 'Billing', order: 40 },\n    { label: 'Master and detail', targetScreen: 'MasterDetailPage', icon: 'pi pi-table', group: 'Billing', order: 50 },\n    { label: 'Register an invoice', targetScreen: 'CommandFormPage', icon: 'pi pi-plus-circle', group: 'Billing', order: 60 },\n    { label: 'Event type schema', targetScreen: 'SchemaEditorPage', icon: 'pi pi-sitemap', group: 'Inspect', order: 10 },\n    { label: 'Invoice document', targetScreen: 'ObjectEditorPage', icon: 'pi pi-file-edit', group: 'Inspect', order: 20 },\n    { label: 'Billing module', targetScreen: 'DataModulePage', icon: 'pi pi-th-large', group: 'Nesting', order: 10 },\n    { label: 'Adjustments feature', targetScreen: 'DataFeatureSection', icon: 'pi pi-folder', group: 'Nesting', order: 20 },\n    { label: 'Record an adjustment', targetScreen: 'CommandSliceSection', icon: 'pi pi-pencil', group: 'Nesting', order: 30 },\n];\n\n/**\n * The navigation as contributions to the `Navigation` contribution point.\n *\n * A screen carries these in its `contributions`, and anything bound to the contribution point recomputes\n * from whatever is currently in scope - so a screen that contributes an extra entry gets it into the\n * navigation without the navigation knowing that screen exists.\n */\nexport const componentsNavigationContributions: Contribution[] = componentsNavigationEntries.map(entry => ({\n    contributionPointName: navigationContributionPoint,\n    content: navigationElement(entry),\n    order: entry.order,\n}));\n\n/** The navigation entries of one group, in order. */\nexport function entriesInGroup(group: string): NavigationEntry[] {\n    return componentsNavigationEntries.filter(entry => entry.group === group).sort((first, second) => first.order - second.order);\n}\n\n/** Every group named by the navigation, in first-declared order. */\nexport const componentsNavigationGroups: string[] = [...new Set(componentsNavigationEntries.map(entry => entry.group))];\n\n/** The section a screen belongs to, for the first entry of its breadcrumb trail. */\nexport function groupOfScreen(screenName: string): string | undefined {\n    return componentsNavigationEntries.find(entry => entry.targetScreen === screenName)?.group;\n}\n\n/** The navigation label of a screen, for the last entry of its breadcrumb trail. */\nexport function labelOfScreen(screenName: string): string | undefined {\n    return componentsNavigationEntries.find(entry => entry.targetScreen === screenName)?.label;\n}\n"],"names":["componentsNavigationEntries","label","targetScreen","icon","group","order","componentsNavigationContributions","map","entry","contributionPointName","navigationContributionPoint","content","navigationElement","entriesInGroup","filter","sort","first","second","componentsNavigationGroups","Set","groupOfScreen","screenName","find","labelOfScreen"],"mappings":";;AAAA;AACA;AAKA;;;;;;;;;;;;UAaaA,2BAAAA,GAAiD;AAC1D,IAAA;QAAEC,KAAAA,EAAO,WAAA;QAAaC,YAAAA,EAAc,eAAA;QAAiBC,IAAAA,EAAM,iBAAA;QAAmBC,KAAAA,EAAO,SAAA;QAAWC,KAAAA,EAAO;AAAG,KAAA;AAC1G,IAAA;QAAEJ,KAAAA,EAAO,UAAA;QAAYC,YAAAA,EAAc,cAAA;QAAgBC,IAAAA,EAAM,YAAA;QAAcC,KAAAA,EAAO,SAAA;QAAWC,KAAAA,EAAO;AAAG,KAAA;AACnG,IAAA;QAAEJ,KAAAA,EAAO,WAAA;QAAaC,YAAAA,EAAc,wBAAA;QAA0BC,IAAAA,EAAM,YAAA;QAAcC,KAAAA,EAAO,SAAA;QAAWC,KAAAA,EAAO;AAAG,KAAA;AAC9G,IAAA;QAAEJ,KAAAA,EAAO,qBAAA;QAAuBC,YAAAA,EAAc,wBAAA;QAA0BC,IAAAA,EAAM,uBAAA;QAAyBC,KAAAA,EAAO,SAAA;QAAWC,KAAAA,EAAO;AAAG,KAAA;AACnI,IAAA;QAAEJ,KAAAA,EAAO,mBAAA;QAAqBC,YAAAA,EAAc,kBAAA;QAAoBC,IAAAA,EAAM,aAAA;QAAeC,KAAAA,EAAO,SAAA;QAAWC,KAAAA,EAAO;AAAG,KAAA;AACjH,IAAA;QAAEJ,KAAAA,EAAO,qBAAA;QAAuBC,YAAAA,EAAc,iBAAA;QAAmBC,IAAAA,EAAM,mBAAA;QAAqBC,KAAAA,EAAO,SAAA;QAAWC,KAAAA,EAAO;AAAG,KAAA;AACxH,IAAA;QAAEJ,KAAAA,EAAO,mBAAA;QAAqBC,YAAAA,EAAc,kBAAA;QAAoBC,IAAAA,EAAM,eAAA;QAAiBC,KAAAA,EAAO,SAAA;QAAWC,KAAAA,EAAO;AAAG,KAAA;AACnH,IAAA;QAAEJ,KAAAA,EAAO,kBAAA;QAAoBC,YAAAA,EAAc,kBAAA;QAAoBC,IAAAA,EAAM,iBAAA;QAAmBC,KAAAA,EAAO,SAAA;QAAWC,KAAAA,EAAO;AAAG,KAAA;AACpH,IAAA;QAAEJ,KAAAA,EAAO,gBAAA;QAAkBC,YAAAA,EAAc,gBAAA;QAAkBC,IAAAA,EAAM,gBAAA;QAAkBC,KAAAA,EAAO,SAAA;QAAWC,KAAAA,EAAO;AAAG,KAAA;AAC/G,IAAA;QAAEJ,KAAAA,EAAO,qBAAA;QAAuBC,YAAAA,EAAc,oBAAA;QAAsBC,IAAAA,EAAM,cAAA;QAAgBC,KAAAA,EAAO,SAAA;QAAWC,KAAAA,EAAO;AAAG,KAAA;AACtH,IAAA;QAAEJ,KAAAA,EAAO,sBAAA;QAAwBC,YAAAA,EAAc,qBAAA;QAAuBC,IAAAA,EAAM,cAAA;QAAgBC,KAAAA,EAAO,SAAA;QAAWC,KAAAA,EAAO;AAAG;;AAG5H;;;;;;UAOaC,iCAAAA,GAAoDN,2BAAAA,CAA4BO,GAAG,CAACC,CAAAA,SAAU;QACvGC,qBAAAA,EAAuBC,2BAAAA;AACvBC,QAAAA,OAAAA,EAASC,iBAAAA,CAAkBJ,KAAAA,CAAAA;AAC3BH,QAAAA,KAAAA,EAAOG,MAAMH;AACjB,KAAA,CAAA;AAEA,sDACO,SAASQ,cAAAA,CAAeT,KAAa,EAAA;AACxC,IAAA,OAAOJ,4BAA4Bc,MAAM,CAACN,CAAAA,KAAAA,GAASA,KAAAA,CAAMJ,KAAK,KAAKA,KAAAA,CAAAA,CAAOW,IAAI,CAAC,CAACC,KAAAA,EAAOC,MAAAA,GAAWD,MAAMX,KAAK,GAAGY,OAAOZ,KAAK,CAAA;AAChI;AAEA,qEACO,MAAMa,0BAAAA,GAAuC;AAAI,IAAA,GAAA,IAAIC,IAAInB,2BAAAA,CAA4BO,GAAG,CAACC,CAAAA,KAAAA,GAASA,MAAMJ,KAAK,CAAA;;AAEpH,qFACO,SAASgB,aAAAA,CAAcC,UAAkB,EAAA;IAC5C,OAAOrB,2BAAAA,CAA4BsB,IAAI,CAACd,CAAAA,QAASA,KAAAA,CAAMN,YAAY,KAAKmB,UAAAA,CAAAA,EAAajB,KAAAA;AACzF;AAEA,qFACO,SAASmB,aAAAA,CAAcF,UAAkB,EAAA;IAC5C,OAAOrB,2BAAAA,CAA4BsB,IAAI,CAACd,CAAAA,QAASA,KAAAA,CAAMN,YAAY,KAAKmB,UAAAA,CAAAA,EAAapB,KAAAA;AACzF;;;;"}

package/dist/esm/gallery/previewProfile.d.ts

@@ -0,0 +1,6 @@
+import { UiProfile } from '@cratis/scene.model';
+import { PackageCatalog } from '@cratis/scene.engine';
+export declare const primeReactComponentNames: string[];
+export declare const componentsBlueprintProfile: UiProfile;
+export declare const componentsBlueprintCatalog: PackageCatalog;
+//# sourceMappingURL=previewProfile.d.ts.map

package/dist/esm/gallery/previewProfile.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"previewProfile.d.ts","sourceRoot":"","sources":["../../../gallery/previewProfile.ts"],"names":[],"mappings":"AAGA,OAAO,EAAE,SAAS,EAAE,MAAM,qBAAqB,CAAC;AAChD,OAAO,EAAE,cAAc,EAAE,MAAM,sBAAsB,CAAC;AAsBtD,eAAO,MAAM,wBAAwB,EAAE,MAAM,EAA4I,CAAC;AAuB1L,eAAO,MAAM,0BAA0B,EAAE,SAIxC,CAAC;AAQF,eAAO,MAAM,0BAA0B,EAAE,cAMxC,CAAC"}

package/dist/esm/gallery/previewProfile.js

@@ -0,0 +1,83 @@
+import { corePackageManifest } from '@cratis/scene.react';
+import { cratisComponentsPackageManifest } from '@cratis/scene.components';
+import { defaultBlueprintName, defaultBlueprintManifest } from '@cratis/scene.blueprint.default';
+import { ComponentName } from '../ComponentName.js';
+import { componentsBlueprintName } from '../packageName.js';
+
+// Copyright (c) Cratis. All rights reserved.
+// Licensed under the MIT license. See LICENSE file in the project root for full license information.
+/**
+ * The names this blueprint borrows from `PrimeReact`.
+ *
+ * Every other package in the catalog below contributes its *real* manifest, because this package takes an
+ * npm dependency on each of them. `PrimeReact` is the exception: this blueprint depends on it in the
+ * manifest sense - `column` comes from there - without depending on its bundle, so its declaration is not
+ * importable here and the borrowed names are written out instead.
+ *
+ * Every name below was checked against `primeReactPackage.ts`'s own component list rather than assumed.
+ * The default blueprint learned why that matters when it referenced `chart` and `fileUpload`, which
+ * neither library declares - names that look obvious and render as dashed red boxes.
+ *
+ * A host that has all five packages loaded should build this catalog from their manifests instead. The
+ * shape is the same, and anything that has drifted then fails this blueprint's specs rather than a preview.
+ */ const primeReactComponentNames = [
+    'column',
+    'dataTable',
+    'table',
+    'dialog',
+    'button',
+    'card',
+    'text',
+    'toolbar',
+    'dropdown',
+    'tooltip',
+    'menu',
+    'breadcrumb',
+    'sidebar'
+];
+/**
+ * The profile this blueprint's templates resolve against.
+ *
+ * Declaration order is ascending priority, which is why this exact order matters rather than being
+ * cosmetic. `Cratis.Components` outranks `PrimeReact`, so a template naming `table` or `dialog` gets the
+ * Arc-aware one and PrimeReact's is recorded as shadowed. Both blueprints outrank both libraries, so
+ * `pageHeader` and `arcPageHeader` resolve to the packages that declare them. And this blueprint sits at
+ * the top, which costs nothing today - it declares one name nobody else does - but is the correct place
+ * for the package doing the layering.
+ *
+ * `core` is listed explicitly rather than left to `effectivePackages` to prepend, because a theme's
+ * compatibility is checked against exactly what a profile declares, and a profile leaning on the implicit
+ * fallback would make a theme look incompatible with a package the profile never admitted to using.
+ *
+ * Unlike the default blueprint, this package needs no separate *preview* profile. That blueprint takes no
+ * npm dependency on the libraries its templates reference, so previewing it from its own package resolves
+ * most names to implementations that are not loaded. This one depends on `@cratis/scene.components` and
+ * `@cratis/scene.blueprint.default` for real, so everything its templates name is loadable except
+ * PrimeReact's `column` - and a `column` never reaches the DOM at design time anyway, because the table it
+ * belongs to is a placeholder until a host registers its query.
+ */ const componentsBlueprintProfile = {
+    name: 'Arc pages',
+    targetPlatform: 'web',
+    packages: [
+        'core',
+        'PrimeReact',
+        cratisComponentsPackageManifest.name,
+        defaultBlueprintName,
+        componentsBlueprintName
+    ]
+};
+/**
+ * The component catalog the templates resolve against.
+ *
+ * Four of the five entries are the owning package's real declared list, read straight off its manifest, so
+ * a name renamed upstream fails a spec here instead of rendering as a dashed box in someone's application.
+ */ const componentsBlueprintCatalog = {
+    [corePackageManifest.name]: corePackageManifest.components,
+    PrimeReact: primeReactComponentNames,
+    [cratisComponentsPackageManifest.name]: cratisComponentsPackageManifest.components,
+    [defaultBlueprintName]: defaultBlueprintManifest.components,
+    [componentsBlueprintName]: Object.values(ComponentName)
+};
+
+export { componentsBlueprintCatalog, componentsBlueprintProfile, primeReactComponentNames };
+//# sourceMappingURL=previewProfile.js.map

package/dist/esm/gallery/previewProfile.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"previewProfile.js","sources":["../../../gallery/previewProfile.ts"],"sourcesContent":["// Copyright (c) Cratis. All rights reserved.\n// Licensed under the MIT license. See LICENSE file in the project root for full license information.\n\nimport { UiProfile } from '@cratis/scene.model';\nimport { PackageCatalog } from '@cratis/scene.engine';\nimport { corePackageManifest } from '@cratis/scene.react';\nimport { cratisComponentsPackageManifest } from '@cratis/scene.components';\nimport { defaultBlueprintManifest, defaultBlueprintName } from '@cratis/scene.blueprint.default';\nimport { ComponentName } from '../ComponentName';\nimport { componentsBlueprintName } from '../packageName';\n\n/**\n * The names this blueprint borrows from `PrimeReact`.\n *\n * Every other package in the catalog below contributes its *real* manifest, because this package takes an\n * npm dependency on each of them. `PrimeReact` is the exception: this blueprint depends on it in the\n * manifest sense - `column` comes from there - without depending on its bundle, so its declaration is not\n * importable here and the borrowed names are written out instead.\n *\n * Every name below was checked against `primeReactPackage.ts`'s own component list rather than assumed.\n * The default blueprint learned why that matters when it referenced `chart` and `fileUpload`, which\n * neither library declares - names that look obvious and render as dashed red boxes.\n *\n * A host that has all five packages loaded should build this catalog from their manifests instead. The\n * shape is the same, and anything that has drifted then fails this blueprint's specs rather than a preview.\n */\nexport const primeReactComponentNames: string[] = ['column', 'dataTable', 'table', 'dialog', 'button', 'card', 'text', 'toolbar', 'dropdown', 'tooltip', 'menu', 'breadcrumb', 'sidebar'];\n\n/**\n * The profile this blueprint's templates resolve against.\n *\n * Declaration order is ascending priority, which is why this exact order matters rather than being\n * cosmetic. `Cratis.Components` outranks `PrimeReact`, so a template naming `table` or `dialog` gets the\n * Arc-aware one and PrimeReact's is recorded as shadowed. Both blueprints outrank both libraries, so\n * `pageHeader` and `arcPageHeader` resolve to the packages that declare them. And this blueprint sits at\n * the top, which costs nothing today - it declares one name nobody else does - but is the correct place\n * for the package doing the layering.\n *\n * `core` is listed explicitly rather than left to `effectivePackages` to prepend, because a theme's\n * compatibility is checked against exactly what a profile declares, and a profile leaning on the implicit\n * fallback would make a theme look incompatible with a package the profile never admitted to using.\n *\n * Unlike the default blueprint, this package needs no separate *preview* profile. That blueprint takes no\n * npm dependency on the libraries its templates reference, so previewing it from its own package resolves\n * most names to implementations that are not loaded. This one depends on `@cratis/scene.components` and\n * `@cratis/scene.blueprint.default` for real, so everything its templates name is loadable except\n * PrimeReact's `column` - and a `column` never reaches the DOM at design time anyway, because the table it\n * belongs to is a placeholder until a host registers its query.\n */\nexport const componentsBlueprintProfile: UiProfile = {\n    name: 'Arc pages',\n    targetPlatform: 'web',\n    packages: ['core', 'PrimeReact', cratisComponentsPackageManifest.name, defaultBlueprintName, componentsBlueprintName],\n};\n\n/**\n * The component catalog the templates resolve against.\n *\n * Four of the five entries are the owning package's real declared list, read straight off its manifest, so\n * a name renamed upstream fails a spec here instead of rendering as a dashed box in someone's application.\n */\nexport const componentsBlueprintCatalog: PackageCatalog = {\n    [corePackageManifest.name]: corePackageManifest.components,\n    PrimeReact: primeReactComponentNames,\n    [cratisComponentsPackageManifest.name]: cratisComponentsPackageManifest.components,\n    [defaultBlueprintName]: defaultBlueprintManifest.components,\n    [componentsBlueprintName]: Object.values(ComponentName),\n};\n"],"names":["primeReactComponentNames","componentsBlueprintProfile","name","targetPlatform","packages","cratisComponentsPackageManifest","defaultBlueprintName","componentsBlueprintName","componentsBlueprintCatalog","corePackageManifest","components","PrimeReact","defaultBlueprintManifest","Object","values","ComponentName"],"mappings":";;;;;;AAAA;AACA;AAUA;;;;;;;;;;;;;;UAeaA,wBAAAA,GAAqC;AAAC,IAAA,QAAA;AAAU,IAAA,WAAA;AAAa,IAAA,OAAA;AAAS,IAAA,QAAA;AAAU,IAAA,QAAA;AAAU,IAAA,MAAA;AAAQ,IAAA,MAAA;AAAQ,IAAA,SAAA;AAAW,IAAA,UAAA;AAAY,IAAA,SAAA;AAAW,IAAA,MAAA;AAAQ,IAAA,YAAA;AAAc,IAAA;;AAE/K;;;;;;;;;;;;;;;;;;;;UAqBaC,0BAAAA,GAAwC;IACjDC,IAAAA,EAAM,WAAA;IACNC,cAAAA,EAAgB,KAAA;IAChBC,QAAAA,EAAU;AAAC,QAAA,MAAA;AAAQ,QAAA,YAAA;AAAcC,QAAAA,+BAAAA,CAAgCH,IAAI;AAAEI,QAAAA,oBAAAA;AAAsBC,QAAAA;AAAwB;AACzH;AAEA;;;;;UAMaC,0BAAAA,GAA6C;AACtD,IAAA,CAACC,mBAAAA,CAAoBP,IAAI,GAAGO,oBAAoBC,UAAU;IAC1DC,UAAAA,EAAYX,wBAAAA;AACZ,IAAA,CAACK,+BAAAA,CAAgCH,IAAI,GAAGG,gCAAgCK,UAAU;IAClF,CAACJ,oBAAAA,GAAuBM,wBAAAA,CAAyBF,UAAU;AAC3D,IAAA,CAACH,uBAAAA,GAA0BM,MAAAA,CAAOC,MAAM,CAACC,aAAAA;AAC7C;;;;"}

package/dist/esm/gallery/screens.d.ts

@@ -0,0 +1,4 @@
+import { Screen } from '@cratis/scene.model';
+export declare const componentsGalleryScreens: Screen[];
+export declare function componentsGalleryScreen(name: string): Screen | undefined;
+//# sourceMappingURL=screens.d.ts.map

package/dist/esm/gallery/screens.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"screens.d.ts","sourceRoot":"","sources":["../../../gallery/screens.ts"],"names":[],"mappings":"AAGA,OAAO,EAAE,MAAM,EAAkB,MAAM,qBAAqB,CAAC;AAkE7D,eAAO,MAAM,wBAAwB,EAAE,MAAM,EAA6C,CAAC;AAG3F,wBAAgB,uBAAuB,CAAC,IAAI,EAAE,MAAM,GAAG,MAAM,GAAG,SAAS,CAExE"}

package/dist/esm/gallery/screens.js

@@ -0,0 +1,77 @@
+import { nestScreenTemplates, LayoutName, templateContentInLayout, appShellLayout } from '@cratis/scene.blueprint.default';
+import '../templates/listTemplates.js';
+import '../templates/workspaceTemplates.js';
+import '../templates/commandTemplates.js';
+import '../templates/editorTemplates.js';
+import { nestingChainTemplates } from '../templates/nesting.js';
+import '../templates/dialogTemplates.js';
+import { componentsScreenTemplates } from '../templates/screenTemplates.js';
+import { componentsApplicationChrome } from './applicationChrome.js';
+import { componentsNavigationContributions } from './navigation.js';
+
+// Copyright (c) Cratis. All rights reserved.
+// Licensed under the MIT license. See LICENSE file in the project root for full license information.
+/**
+ * The gallery: one {@link Screen} per template, ready to boot through the real engine.
+ *
+ * These exist so a preview is a working miniature application rather than a set of pictures - the same
+ * `Screen` shape Stage produces, put through the same `Scene.Engine` and `Scene.React`, with no separate
+ * preview pipeline and nothing mocked.
+ *
+ * They will render with unregistered bindings, and that is the normal design-time state rather than a
+ * shortcoming of the gallery. A host owns the generated Arc proxies; a gallery is not a host. What a
+ * preview therefore shows is every Arc-bound region as a placeholder naming the binding it wanted, every
+ * Arc-free region rendered for real, and a header on each page saying which of the two you are looking at.
+ *
+ * Every screen renders in the default blueprint's `AppShell`. There is no full-page variant here because
+ * there is no Arc-bound page that belongs outside the application shell - a sign-in screen queries nothing
+ * and submits no command, so it stays where it already is, in the default blueprint.
+ */ /**
+ * Builds the {@link Screen} that instantiates one template.
+ *
+ * A screen is an instance, not a shape: it names the layout it renders in, the template it fills, the
+ * content that fills it, and what it contributes elsewhere. Everything structural comes from the template,
+ * which is why adding a screen is a handful of lines rather than another copy of the chrome.
+ */ function screenFor(template) {
+    const placeable = nestScreenTemplates(containmentChainFor(template));
+    return {
+        name: template.name,
+        layout: LayoutName.AppShell,
+        screenTemplate: template.name,
+        slotContent: mergeSlotContent(componentsApplicationChrome(template.name), templateContentInLayout(placeable, appShellLayout)),
+        forms: [],
+        contributions: componentsNavigationContributions
+    };
+}
+/**
+ * The chain of templates a screen renders through, outermost first.
+ *
+ * The eight page templates fit the layout's own `content` slot, so each one's chain is just itself. The
+ * three nesting-chain templates are the exception and the only ones that need the walk - which is the
+ * honest version of the story: nesting exists for the applications that need it, and costs nothing for the
+ * ones that do not.
+ */ function containmentChainFor(template) {
+    const depth = nestingChainTemplates.findIndex((candidate)=>candidate.name === template.name);
+    return depth < 0 ? [
+        template
+    ] : nestingChainTemplates.slice(0, depth + 1);
+}
+function mergeSlotContent(chrome, content) {
+    const merged = {
+        ...chrome
+    };
+    for (const [slotName, elements] of Object.entries(content)){
+        merged[slotName] = [
+            ...merged[slotName] ?? [],
+            ...elements
+        ];
+    }
+    return merged;
+}
+/** One screen per screen template this blueprint provides. */ const componentsGalleryScreens = componentsScreenTemplates.map(screenFor);
+/** One gallery screen by name, for a story or a host that boots a specific one. */ function componentsGalleryScreen(name) {
+    return componentsGalleryScreens.find((screen)=>screen.name === name);
+}
+
+export { componentsGalleryScreen, componentsGalleryScreens };
+//# sourceMappingURL=screens.js.map

package/dist/esm/gallery/screens.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"screens.js","sources":["../../../gallery/screens.ts"],"sourcesContent":["// Copyright (c) Cratis. All rights reserved.\n// Licensed under the MIT license. See LICENSE file in the project root for full license information.\n\nimport { Screen, ScreenTemplate } from '@cratis/scene.model';\nimport { LayoutName, appShellLayout, nestScreenTemplates, templateContentInLayout } from '@cratis/scene.blueprint.default';\nimport { componentsScreenTemplates, nestingChainTemplates } from '../templates';\nimport { componentsApplicationChrome } from './applicationChrome';\nimport { componentsNavigationContributions } from './navigation';\n\n/**\n * The gallery: one {@link Screen} per template, ready to boot through the real engine.\n *\n * These exist so a preview is a working miniature application rather than a set of pictures - the same\n * `Screen` shape Stage produces, put through the same `Scene.Engine` and `Scene.React`, with no separate\n * preview pipeline and nothing mocked.\n *\n * They will render with unregistered bindings, and that is the normal design-time state rather than a\n * shortcoming of the gallery. A host owns the generated Arc proxies; a gallery is not a host. What a\n * preview therefore shows is every Arc-bound region as a placeholder naming the binding it wanted, every\n * Arc-free region rendered for real, and a header on each page saying which of the two you are looking at.\n *\n * Every screen renders in the default blueprint's `AppShell`. There is no full-page variant here because\n * there is no Arc-bound page that belongs outside the application shell - a sign-in screen queries nothing\n * and submits no command, so it stays where it already is, in the default blueprint.\n */\n\n/**\n * Builds the {@link Screen} that instantiates one template.\n *\n * A screen is an instance, not a shape: it names the layout it renders in, the template it fills, the\n * content that fills it, and what it contributes elsewhere. Everything structural comes from the template,\n * which is why adding a screen is a handful of lines rather than another copy of the chrome.\n */\nfunction screenFor(template: ScreenTemplate): Screen {\n    const placeable = nestScreenTemplates(containmentChainFor(template));\n\n    return {\n        name: template.name,\n        layout: LayoutName.AppShell,\n        screenTemplate: template.name,\n        slotContent: mergeSlotContent(componentsApplicationChrome(template.name), templateContentInLayout(placeable, appShellLayout)),\n        forms: [],\n        contributions: componentsNavigationContributions,\n    };\n}\n\n/**\n * The chain of templates a screen renders through, outermost first.\n *\n * The eight page templates fit the layout's own `content` slot, so each one's chain is just itself. The\n * three nesting-chain templates are the exception and the only ones that need the walk - which is the\n * honest version of the story: nesting exists for the applications that need it, and costs nothing for the\n * ones that do not.\n */\nfunction containmentChainFor(template: ScreenTemplate): ScreenTemplate[] {\n    const depth = nestingChainTemplates.findIndex(candidate => candidate.name === template.name);\n    return depth < 0 ? [template] : nestingChainTemplates.slice(0, depth + 1);\n}\n\nfunction mergeSlotContent(chrome: Record<string, Screen['slotContent'][string]>, content: Record<string, Screen['slotContent'][string]>): Screen['slotContent'] {\n    const merged: Screen['slotContent'] = { ...chrome };\n    for (const [slotName, elements] of Object.entries(content)) {\n        merged[slotName] = [...(merged[slotName] ?? []), ...elements];\n    }\n\n    return merged;\n}\n\n/** One screen per screen template this blueprint provides. */\nexport const componentsGalleryScreens: Screen[] = componentsScreenTemplates.map(screenFor);\n\n/** One gallery screen by name, for a story or a host that boots a specific one. */\nexport function componentsGalleryScreen(name: string): Screen | undefined {\n    return componentsGalleryScreens.find(screen => screen.name === name);\n}\n"],"names":["screenFor","template","placeable","nestScreenTemplates","containmentChainFor","name","layout","LayoutName","AppShell","screenTemplate","slotContent","mergeSlotContent","componentsApplicationChrome","templateContentInLayout","appShellLayout","forms","contributions","componentsNavigationContributions","depth","nestingChainTemplates","findIndex","candidate","slice","chrome","content","merged","slotName","elements","Object","entries","componentsGalleryScreens","componentsScreenTemplates","map","componentsGalleryScreen","find","screen"],"mappings":";;;;;;;;;;;AAAA;AACA;AAQA;;;;;;;;;;;;;;;;;;;;;IAwBA,SAASA,UAAUC,QAAwB,EAAA;IACvC,MAAMC,SAAAA,GAAYC,oBAAoBC,mBAAAA,CAAoBH,QAAAA,CAAAA,CAAAA;IAE1D,OAAO;AACHI,QAAAA,IAAAA,EAAMJ,SAASI,IAAI;AACnBC,QAAAA,MAAAA,EAAQC,WAAWC,QAAQ;AAC3BC,QAAAA,cAAAA,EAAgBR,SAASI,IAAI;AAC7BK,QAAAA,WAAAA,EAAaC,iBAAiBC,2BAAAA,CAA4BX,QAAAA,CAASI,IAAI,CAAA,EAAGQ,wBAAwBX,SAAAA,EAAWY,cAAAA,CAAAA,CAAAA;AAC7GC,QAAAA,KAAAA,EAAO,EAAE;QACTC,aAAAA,EAAeC;AACnB,KAAA;AACJ;AAEA;;;;;;;IAQA,SAASb,oBAAoBH,QAAwB,EAAA;IACjD,MAAMiB,KAAAA,GAAQC,qBAAAA,CAAsBC,SAAS,CAACC,CAAAA,YAAaA,SAAAA,CAAUhB,IAAI,KAAKJ,QAAAA,CAASI,IAAI,CAAA;AAC3F,IAAA,OAAOa,QAAQ,CAAA,GAAI;AAACjB,QAAAA;AAAS,KAAA,GAAGkB,qBAAAA,CAAsBG,KAAK,CAAC,CAAA,EAAGJ,KAAAA,GAAQ,CAAA,CAAA;AAC3E;AAEA,SAASP,gBAAAA,CAAiBY,MAAqD,EAAEC,OAAsD,EAAA;AACnI,IAAA,MAAMC,MAAAA,GAAgC;AAAE,QAAA,GAAGF;AAAO,KAAA;IAClD,KAAK,MAAM,CAACG,QAAAA,EAAUC,QAAAA,CAAS,IAAIC,MAAAA,CAAOC,OAAO,CAACL,OAAAA,CAAAA,CAAU;QACxDC,MAAM,CAACC,SAAS,GAAG;eAAKD,MAAM,CAACC,QAAAA,CAAS,IAAI,EAAE;AAAMC,YAAAA,GAAAA;AAAS,SAAA;AACjE,IAAA;IAEA,OAAOF,MAAAA;AACX;AAEA,+DACO,MAAMK,2BAAqCC,yBAAAA,CAA0BC,GAAG,CAAChC,SAAAA;AAEhF,oFACO,SAASiC,uBAAAA,CAAwB5B,IAAY,EAAA;AAChD,IAAA,OAAOyB,yBAAyBI,IAAI,CAACC,CAAAA,MAAAA,GAAUA,MAAAA,CAAO9B,IAAI,KAAKA,IAAAA,CAAAA;AACnE;;;;"}