Panes

​

Sources

​

Structure

• A Plot Pane owns the Plots it draws. Its type, in scalar-lib types, is the kind of the rows of the one Plot its Perception does not declare. Each other Plot declares its own contract. A computation that other Panes read, or that has its own lifecycle, gets a Pane of its own, and the Plots that need it read it by name.
• A bound Pane has no SQL. One field of its parent’s row feeds it as props.value, and it uses its parent’s Policies (Bound Panes).
• A saved-data Pane has no SQL. Its type has an id field, and the values people save on it are Preferences: rows of its type, one for each item and each actor. A Plot on a saved-data Pane would make it a Plot Pane that refuses every save of a row, so the saved-data-plot rule refuses it. Give the Plot a Pane of its own.
• A layout Pane has a null type, so it holds no saved rows.

​

Warnings & Errors

​

A Pane that does not build

​

Fixing Warnings & Errors with Ponder

​

Checking that Panes draw

• placed: false when no Page shows the Pane (the unplaced-pane note).
• drawsWithoutInput: false when the Pane waits for a value that no parent hands it (the needs-input note), and acceptsNull from its runtime binding.
• resolution: what panes/resolve gives the Pane with no Preference selected, or why it refuses the Pane.
• plots: the rows each Plot of the Pane returns, at most 50 for each Plot, and at most 20 Plots for each check. A read that fails gives its reason. A Plot that takes inputs uses its saved parameters. When it has none, the check reads it with null for each input.
• diagnostics: the counts that Read a Piece’s problems reads.

​

Services

​

Storage

​

Security

​

What a Pane’s code can reach

​

Changes that apply at once

1. The change is an edit of Pane data (propose.change with data). A change to Policies or SQL, and a new Plot (propose.piece), still ask.
2. The Parable has Published Versions. On a Personal Parable a change is live at once, so it still asks.
3. The reader holds Publishing or Primary.
4. Each person who saved code that the frame draws saved it on this Parable. Code that came with a Release from the Parable a copy comes from still asks. The frame runs the Parable’s own code, or the code of the Patch that the change goes into. Code that a colleague saved in their own Patch still asks. Code that a colleague saved in the reader’s own Patch still asks too. A colleague with Publishing who sees a Problem that a person started can save code into its Patch. So the reader must have saved each Page and Pane code in the Patch that differs from the Parable’s own code.
5. The reader may view the changed Pane’s data, so the banner can list each item.
6. The change goes into a Patch that the reader started and that is still Pending. With no Patch named, the server picks the reader’s newest Pending Patch or opens one in a new Problem, Changes from the Pane’s name. A colleague’s Patch still asks.

​

Files in Pane code

import { useEffect, useState } from 'react';
import { files, type PaneFile } from '@parable/perceptions/actorFiles';
import { Button } from 'parable/panes/placeholders';

export default function ActorFiles() {
  const [list, setList] = useState<readonly PaneFile[]>([]);
  const [error, setError] = useState<string | null>(null);
  useEffect(() => {
    files.list({ kind: 'data' }).then(setList, failure => setError(failure.message));
  }, []);
  const add = () =>
    files
      .upload({ kinds: ['data'] })
      .then(() => files.list({ kind: 'data' }))
      .then(setList, failure => setError(failure.message));
  return (
    <div className="parable-pane">
      <Button onClick={add}>Add a data file</Button>
      {error ? <p>{error}</p> : null}
      <ul>
        {list.map(file => (
          <li key={file.id}>
            {file.name}: {file.table?.address ?? 'no table'}
          </li>
        ))}
      </ul>
    </div>
  );
}

​

The Workspace’s files

1. The Pane declares that its code reads the Workspace’s files. Its Perception holds readonly workspaceFiles: true;. A Pane’s code asks for its own Pane. A Page’s code asks for the Page, so the Page’s Perception holds the declaration.
2. Only a person whose Workspace role lists the Workspace’s files saves a Perception that declares it: the role holds the permission to view Artifacts or to upload them. The rule applies to each save that changes a Perception and keeps the declaration in it: an edit in the Parable editor, an edit from Ponder, a change from Pane code, and an archive import. A save that keeps the stored Perception, or that removes the declaration, needs no such permission.
3. Every person who last saved code that runs in the Page’s frame holds the Workspace’s permission to view Artifacts or to upload them. The code in the frame is the code of the Page and of each Pane that it renders. On a copy, code that was saved on the Parable the copy comes from never reads the copy Workspace’s files. When any code in the frame comes from there, the server refuses.

export interface Perception extends BasePerception<Budget> {
  readonly workspaceFiles: true;
  readonly panes: {};
}

​

Pane-started runs

• Preview. This Pane asked to preview too often. Try again in 10 seconds.
• Run. This Pane asked to run too often. Try again in a minute.