@formicoidea/labre-framework-edgy 0.41.0 → 0.43.1

package/dist/translations.js

@@ -1,6 +1,5 @@
 import { collectTranslationKeys, commandCategoryTranslationEntries, commandTranslationEntries, mergeTranslationEntries, } from '@formicoidea/labre-core/std';
-import { edgyCommands } from './commands.js';
-import { EDGY_LEGEND_CHROME_WORDINGS } from './legend.js';
+import { edgyCommands, EDGY_LEGEND_CHROME_WORDINGS } from './commands.js';
 import { EDGY_DYNAMIC_NODES, EDGY_DYNAMIC_VERBS, EDGY_ZONES, edgyElementLabel, edgyElementLabelKey, edgyVerbSeedKey, } from './metamodel.js';
 import { NODE_LABEL, nodeLabelKey } from './node/consts.js';
 import { EDGY_NUDGES } from './nudges.js';

package/dist/view.js

@@ -1,8 +1,8 @@
-import { QualityNudgeExtension, ReadingProfileExtension, SpotlightHostExtension, ValidationProfileExtension, ValidationRuleExtension, validationToolbarConfig, } from '@formicoidea/labre-core/blocks/surface';
-import { ToolbarModuleExtension } from '@formicoidea/labre-core/shared/services';
+import { QualityNudgeExtension, ReadingProfileExtension, SpotlightHostExtension, ValidationProfileExtension, ValidationRuleExtension, } from '@formicoidea/labre-core/blocks/surface';
+import { FrameworkPaletteExtension } from '@formicoidea/labre-core/components/color-picker';
 import { ViewExtensionProvider, } from '@formicoidea/labre-core/ext-loader';
 import { TemplateCategoryExtension } from '@formicoidea/labre-core/gfx/template';
-import { BlockFlavourIdentifier, CommandExtension } from '@formicoidea/labre-core/std';
+import { CommandExtension } from '@formicoidea/labre-core/std';
 import { RoleVocabularyExtension } from '@formicoidea/labre-core/std/gfx';
 import { edgyCommandIcons, edgyCommands } from './commands.js';
 import { effects } from './effects.js';
@@ -19,8 +19,8 @@ import { EdgyFacetsRendererExtension } from './element-renderer.js';
 import { EdgyInteraction, EdgyView } from './element-view.js';
 import { EdgyNodeRendererExtension } from './node/node-renderer.js';
 import { EdgyNodeView } from './node/node-view.js';
-import { edgyBoardToolbarExtension, edgyToolbarExtension, } from './toolbar/config.js';
-import { edgyNodeToolbarExtension } from './toolbar/node-config.js';
+import { edgyBoardToolbarExtension, edgyBoardToolingToolbarExtension, edgyToolbarExtension, edgyToolingToolbarExtension, } from './toolbar/config.js';
+import { EDGY_FRAMEWORK_PALETTE, edgyNodeToolbarExtension, } from './toolbar/node-config.js';
 import { edgySeniorTool } from './toolbar/senior-tool.js';
 /**
  * EDGY rendering — ALWAYS registered, independent of any flag. Disabling `edgy`
@@ -88,22 +88,17 @@ export class EdgyViewExtension extends ViewExtensionProvider {
             // including the two the PO deliberately kept out of `rules.ts` on
             // 26/08/2026 (see `./nudges.ts`).
             context.register(QualityNudgeExtension(EDGY_NUDGES));
-            // The Validation dropdown on a selected background's contextual toolbar.
-            // A SECOND module on the same element, through the `custom:` flavour slot
-            // (the pattern `gfx/wardley` uses on its map): the rendering toolbars are
-            // registered always-on because a stored board must keep its toggles,
-            // while choosing how hard to check it is tooling and belongs here. The
-            // config itself names no framework — it reads roles and profiles — so
-            // BOTH EDGY frames register the very same object.
-            for (const flavour of [
-                'custom:affine:surface:edgy',
-                'custom:affine:surface:edgyBoard',
-            ]) {
-                context.register(ToolbarModuleExtension({
-                    id: BlockFlavourIdentifier(flavour),
-                    config: validationToolbarConfig,
-                }));
-            }
+            // The LEGEND button and the Validation dropdown on a selected
+            // background's contextual toolbar. A SECOND module on the same element,
+            // through the `custom:` flavour slot (the pattern `gfx/wardley` uses on
+            // its map): the rendering toolbars are registered always-on because a
+            // stored board must keep its appearance toggles, while asking the
+            // framework what its notation means, and choosing how hard to check the
+            // board, are both tooling and belong here (`docs/adr/0026`). One module
+            // per frame and not one shared object, because the button has to know
+            // WHICH background it is documenting.
+            context.register(edgyToolingToolbarExtension);
+            context.register(edgyBoardToolingToolbarExtension);
             // The resolver that turns a hand-drawn `edgy:relation` into the verb the
             // metamodel gives its two ends. It belongs HERE and not in the always-on
             // extension above, and the test is the one `docs/adr/0009` asks: does it
@@ -122,6 +117,11 @@ export class EdgyViewExtension extends ViewExtensionProvider {
             // profile, so it goes with the flag without either side naming the other.
             context.register(ReadingProfileExtension(EDGY_READING));
             context.register(edgySeniorTool);
+            // EDGY's page of the colour pickers' carousel (`docs/adr/0027`). Here,
+            // beside the senior tool, because offering hues is TOOLING — the colours
+            // already painted on a stored board are content and do not move
+            // (`docs/adr/0009`).
+            context.register(FrameworkPaletteExtension(EDGY_FRAMEWORK_PALETTE));
             // The Templates-panel category — tooling, so it goes with the flag (#244).
             context.register(TemplateCategoryExtension(edgyTemplateCategory));
             // The eight EDGY commands: the sub-menu renders them, Settings ›

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@formicoidea/labre-framework-edgy",
   "description": "Labre edgy framework for @formicoidea/labre-core.",
-  "version": "0.41.0",
+  "version": "0.43.1",
   "type": "module",
   "sideEffects": false,
   "author": "lajola",
@@ -31,8 +31,7 @@
     "dist"
   ],
   "dependencies": {
-    "@formicoidea/labre-core": "0.41.0",
-    "@formicoidea/labre-ddd-shared": "0.41.0",
+    "@formicoidea/labre-core": "0.43.1",
     "@preact/signals-core": "^1.8.0",
     "lit": "^3.2.0",
     "yjs": "^13.6.21"

package/dist/legend.d.ts

@@ -1,11 +0,0 @@
-import { type AutoLegendSpec } from '@formicoidea/labre-ddd-shared';
-import { type ChromeWording } from '@formicoidea/labre-core/shared/services';
-/**
- * The two section titles above that are this framework's OWN word rather than
- * a role's — `titleKey` reuses a role's key where the section says a role's
- * name (the facets, the intersections), but "Base elements" and "Relations"
- * name a GROUPING of roles, so each mints a key of its own. For
- * `translations.ts`'s manifest.
- */
-export declare const EDGY_LEGEND_CHROME_WORDINGS: readonly ChromeWording[];
-export declare const EDGY_AUTO_LEGEND: AutoLegendSpec;

package/dist/legend.js

@@ -1,133 +0,0 @@
-import { roleLabel, } from '@formicoidea/labre-ddd-shared';
-import { BOARD_LEGEND_TITLE, } from '@formicoidea/labre-core/shared/services';
-import { EDGY_DYNAMIC_NODES, EDGY_ZONE_FILL, EDGY_ZONES, edgyElementLabel, edgyElementLabelKey, } from './metamodel.js';
-import { NODE_FILL, NODE_STROKE } from './node/consts.js';
-import { EDGY_ROLE, EDGY_ROLES } from './roles.js';
-/**
- * What an EDGY background's automatic legend can say — a TABLE, and nothing
- * else: the scan, the placement and the box are `createAutoLegend`'s job, the
- * same generic the three DDD backgrounds were given
- * (`@labre/affine-gfx-ddd-shared`, `shared/legend-auto.ts`). EDGY takes a
- * dependency on that package for the generic and the box prefab alone; moving
- * them to a neutral home would be the tidier answer and is not worth the churn
- * of this fix.
- *
- * Every row is DERIVED — from the metamodel (`./metamodel.ts`: which elements
- * exist, which zone each belongs to, what colour that zone is drawn in) and
- * from the role vocabulary's own labels (`./roles.ts`). Nothing here is
- * restated: a thirteenth element added to the metamodel gets its legend row the
- * same way it gets its role, with no edit to this file.
- *
- * ## The order
- *
- * By ZONE, and the order of the table carries it: the three facets first
- * (Identity, Architecture, Experience), then the three intersections in one
- * section, then the four base elements, then the relations — which is the
- * reading order of {@link EDGY_ZONES} and, before it, of the Venn itself.
- */
-/** One row per official element of `zone`, in the metamodel's own order. */
-function zoneEntries(zone) {
-    return Object.entries(EDGY_DYNAMIC_NODES)
-        .filter(([, node]) => node.zone === zone)
-        .map(([name]) => ({
-        role: EDGY_ROLE[name],
-        row: {
-            swatch: 'square',
-            // The zone's fill, which IS what the diagram paints the element with.
-            color: EDGY_ZONE_FILL[zone],
-            label: roleLabel(EDGY_ROLES, EDGY_ROLE[name]),
-        },
-    }));
-}
-/**
- * A facet's section title says the facet's own name, so it reuses the key the
- * metamodel's seeds already carry (`edgyElementLabelKey`): the legend and the
- * facets diagram say "Identity" with one key, not two.
- */
-const FACET_SECTIONS = EDGY_ZONES.filter(zone => zone.group === 'facet').map(zone => ({
-    title: edgyElementLabel(zone.id),
-    titleKey: edgyElementLabelKey(zone.id),
-    entries: zoneEntries(zone.id),
-}));
-/**
- * The three intersection elements in ONE section: Organisation, Product and
- * Brand are not three facets, they are the three lenses between them, and the
- * diagram says so by drawing them in the overlaps. Each keeps its own colour.
- */
-const INTERSECTIONS_SECTION = {
-    title: 'Intersections',
-    titleKey: 'com.labre.edgy.seed.intersections-title',
-    entries: EDGY_ZONES.filter(zone => zone.group === 'intersection').flatMap(zone => zoneEntries(zone.id)),
-};
-/**
- * The four base elements, listed only when one is on the board BARE — an
- * element the user dropped from the toolbox and left as a People, an Outcome,
- * an Object or an Activity, without saying which of the twelve it is. White,
- * because that is the fill the palette gives them (`node/consts.ts`).
- *
- * `exact` is what makes "bare" true. Detection is otherwise an ancestor walk,
- * and the twelve official elements specialise these four — Content is an
- * object, Story an activity — so an "Object" row would appear on a board
- * carrying nothing but Contents, keyed to a white swatch that is drawn nowhere
- * on it. The relation entry below keeps the walk, because there the parent row
- * IS the fair summary: a board carrying `edgy:expresses` carries a relation.
- */
-const BASE_SECTION = {
-    title: 'Base elements',
-    titleKey: 'com.labre.edgy.legend.section.base-elements',
-    entries: ['people', 'outcome', 'object', 'activity'].map(kind => ({
-        role: EDGY_ROLE[kind],
-        exact: true,
-        row: {
-            swatch: 'square',
-            color: NODE_FILL,
-            label: roleLabel(EDGY_ROLES, EDGY_ROLE[kind]),
-        },
-    })),
-};
-/**
- * ONE row for the whole relation family, keyed on the PARENT role: a board
- * carrying "content expresses purpose" carries `edgy:expresses`, which is a
- * relation, and that is all the legend has to say. Twenty-two rows naming the
- * verbs would restate the metamodel rather than document the drawing — and the
- * verb travels on the link itself, visible, where it belongs.
- */
-const RELATIONS_SECTION = {
-    title: 'Relations',
-    titleKey: 'com.labre.edgy.legend.section.relations',
-    entries: [
-        {
-            role: EDGY_ROLE.relation,
-            row: {
-                swatch: 'line',
-                // The stroke `activateEdgyRelation` arms the connector tool with.
-                color: NODE_STROKE,
-                label: roleLabel(EDGY_ROLES, EDGY_ROLE.relation),
-            },
-        },
-    ],
-};
-/**
- * The two section titles above that are this framework's OWN word rather than
- * a role's — `titleKey` reuses a role's key where the section says a role's
- * name (the facets, the intersections), but "Base elements" and "Relations"
- * name a GROUPING of roles, so each mints a key of its own. For
- * `translations.ts`'s manifest.
- */
-export const EDGY_LEGEND_CHROME_WORDINGS = [
-    ['com.labre.edgy.legend.section.base-elements', 'Base elements'],
-    ['com.labre.edgy.legend.section.relations', 'Relations'],
-];
-export const EDGY_AUTO_LEGEND = {
-    // The shared DDD auto-legend box's own generic chrome, resolved through
-    // the same key every board that has one reuses — see `AutoLegendSpec.title`.
-    title: BOARD_LEGEND_TITLE[1],
-    titleKey: BOARD_LEGEND_TITLE[0],
-    roles: EDGY_ROLES,
-    sections: [
-        ...FACET_SECTIONS,
-        INTERSECTIONS_SECTION,
-        BASE_SECTION,
-        RELATIONS_SECTION,
-    ],
-};