@broadpaper/editor 0.2.1 → 0.4.0

package/dist/styles.css

@@ -188,7 +188,11 @@
 .bpe-input--invalid { border-color: var(--bpe-danger) !important; }
 .bpe-textarea { height: auto; min-height: 56px; padding: 6px 8px; resize: vertical; line-height: 1.45; }
 .bpe-select { appearance: none; padding-right: 24px; background-image: url("data:image/svg+xml;utf8,<svg xmlns='http://www.w3.org/2000/svg' width='10' height='6' viewBox='0 0 10 6'><path d='M1 1l4 4 4-4' fill='none' stroke='%236b7280' stroke-width='1.5' stroke-linecap='round'/></svg>"); background-repeat: no-repeat; background-position: right 8px center; }
-.bpe-input-group { position: relative; display: flex; align-items: center; }
+/* `width: 100%`, because a flex container sizes to its content and this one holds
+   an input. Without it every field with a unit or a suffix — a width in `%`, a
+   size in `px` — shrank to about twenty characters and left the rest of the row
+   blank, while the plain inputs beside it filled. */
+.bpe-input-group { position: relative; display: flex; align-items: center; width: 100%; }
 .bpe-input-group .bpe-input { padding-right: 28px; }
 .bpe-input-group__suffix { position: absolute; right: 8px; font-size: var(--bpe-text-xs); color: var(--bpe-fg-faint); pointer-events: none; }
 .bpe-input-group__btn { position: absolute; right: 2px; top: 2px; }
@@ -536,14 +540,49 @@
 .bpe-binding__btn { display: flex; align-items: center; gap: 6px; flex: 1; min-width: 0; height: var(--bpe-control-h); padding: 0 8px; border: 1px solid var(--bpe-border); border-radius: var(--bpe-radius); background: var(--bpe-bg); text-align: left; font-size: var(--bpe-text-sm); }
 .bpe-binding__btn:hover { border-color: var(--bpe-border-strong); }
 .bpe-binding__btn--empty { color: var(--bpe-fg-faint); }
+/* A value the document works out. Shown, named after the fields it reads, and not
+   editable where there is no expression editor to edit it with. */
+.bpe-binding__btn--locked { background: var(--bpe-bg-subtle); color: var(--bpe-fg-muted); cursor: default; }
+.bpe-binding__btn--locked:hover { border-color: var(--bpe-border); }
 .bpe-binding__btn svg { width: 13px; height: 13px; flex-shrink: 0; color: var(--bpe-fg-muted); }
 .bpe-expr { font-family: var(--bpe-font-mono); font-size: 11px; }
 .bpe-picker { width: 300px; max-height: 380px; display: flex; flex-direction: column; padding: 0; overflow: hidden; }
+/* Wider when it is holding the calculation builder, which is three controls on a
+   row plus a field name. At 300px every one of them truncated — "a total",
+   "Total of", "In…" — so the panel read as an interface that had been broken
+   rather than one that was cramped. The field list on the other tab is a single
+   column and does not need it, but one width for the panel is better than a
+   popover that changes size when you change tab. */
+.bpe-picker--wide { width: 420px; max-height: 460px; }
 .bpe-picker__search { padding: 8px; border-bottom: 1px solid var(--bpe-border); }
 .bpe-picker__list { flex: 1; overflow-y: auto; padding: 4px; }
 .bpe-picker__foot { display: flex; gap: 6px; align-items: center; padding: 8px; border-top: 1px solid var(--bpe-border); }
 .bpe-picker__foot .bpe-input { flex: 1; }
 .bpe-picker__group { padding: 6px 6px 2px; font-size: var(--bpe-text-xs); font-weight: 600; text-transform: uppercase; letter-spacing: 0.05em; color: var(--bpe-fg-faint); }
+/* The value panel's two answers: a field, or a value worked out. Shorter than the
+   inspector's own tabs because these carry a word rather than a word and an icon. */
+.bpe-picker__tabs { display: flex; gap: 2px; padding: 6px 6px 0; border-bottom: 1px solid var(--bpe-border); }
+.bpe-picker__tabs .bpe-tab { height: 28px; }
+
+/* The calculation builder. A column of rows, each reading as part of a sentence,
+   and every control allowed to shrink — the properties panel is resizable, so
+   anything in it can be squeezed and `min-width: 0` is what keeps the remove
+   button inside the panel rather than out through its `overflow: hidden`. */
+.bpe-calc { display: flex; flex-direction: column; gap: 10px; padding: 10px; min-width: 0; }
+/* A step is a labelled block, not a line of controls.
+   Three selects and a field name across one row is what made this unreadable:
+   every control shrank to its truncation point and the sentence the builder is
+   supposed to read as was unrecoverable from the abbreviations. */
+.bpe-calc__step { display: flex; flex-direction: column; gap: 4px; min-width: 0; padding: 8px; border: 1px solid var(--bpe-border); border-radius: var(--bpe-radius); background: var(--bpe-bg-subtle); }
+.bpe-calc__row { display: flex; align-items: center; gap: 6px; min-width: 0; }
+.bpe-grow { flex: 1 1 auto; }
+.bpe-calc__lead { flex: 0 0 auto; font-size: var(--bpe-text-xs); font-weight: 600; text-transform: uppercase; letter-spacing: 0.04em; color: var(--bpe-fg-faint); }
+.bpe-calc__row .bpe-select { flex: 1 1 auto; min-width: 0; }
+.bpe-calc__term { display: flex; flex-direction: column; gap: 4px; min-width: 0; }
+.bpe-calc__term .bpe-binding { width: 100%; }
+.bpe-calc__term .bpe-binding__btn { flex: 1 1 auto; min-width: 0; }
+.bpe-calc__term .bpe-input { width: 100%; }
+.bpe-calc__reads { margin: 2px 0 0; padding-top: 8px; border-top: 1px solid var(--bpe-border); font-size: var(--bpe-text-xs); color: var(--bpe-fg-muted); line-height: 1.5; }
 .bpe-cond { display: flex; flex-direction: column; gap: 6px; min-width: 0; }
 .bpe-cond__rule { display: grid; grid-template-columns: minmax(0, 1fr) auto; gap: 4px; min-width: 0; padding: 6px; border: 1px solid var(--bpe-border); border-radius: var(--bpe-radius); background: var(--bpe-bg-subtle); }
 .bpe-cond__row { display: grid; grid-template-columns: minmax(0, 1fr); gap: 4px; min-width: 0; }
@@ -555,6 +594,17 @@
 .bpe-list-editor__head .bpe-truncate { flex: 1 1 0; min-width: 0; }
 .bpe-list-editor__item { min-width: 0; }
 .bpe-list-editor__body { padding: 6px 8px 8px; border-top: 1px solid var(--bpe-border); display: flex; flex-direction: column; gap: 6px; }
+/*
+ * Inside a list item, every field is stacked.
+ *
+ * The two-column field — a 96px label and the control beside it — is right in the
+ * panel and wrong one level in: the item is already indented and bordered, so the
+ * label column eats a third of what is left and the control ends in the middle of
+ * the row with the rest blank. Stacked gives the control the whole width, and it
+ * matches the fields in there that were already stacked because they needed it.
+ */
+.bpe-list-editor__body .bpe-field { grid-template-columns: 1fr; gap: 4px; }
+.bpe-list-editor__body .bpe-field__label { white-space: normal; overflow: visible; }
 .bpe-list-editor__drag { cursor: grab; color: var(--bpe-fg-faint); display: inline-flex; }
 .bpe-issue { display: flex; gap: 8px; align-items: flex-start; width: 100%; padding: 6px 8px; border: 0; border-radius: var(--bpe-radius-sm); background: transparent; text-align: left; font-size: var(--bpe-text-sm); color: var(--bpe-fg); }
 .bpe-issue:hover { background: var(--bpe-bg-muted); }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@broadpaper/editor",
-  "version": "0.2.1",
+  "version": "0.4.0",
   "description": "BroadPaper visual report designer. Framework-neutral mount API; React inside.",
   "keywords": [
     "pdf",
@@ -55,9 +55,9 @@
     "prosemirror-view": "^1.37.1",
     "react": "^19.0.0",
     "react-dom": "^19.0.0",
-    "@broadpaper/core": "0.2.1",
-    "@broadpaper/renderer": "0.2.1",
-    "@broadpaper/blocks": "0.2.1"
+    "@broadpaper/blocks": "0.4.0",
+    "@broadpaper/core": "0.4.0",
+    "@broadpaper/renderer": "0.4.0"
   },
   "devDependencies": {
     "@types/react": "^19.0.2",