nextspace
    Preparing search index...

    Interface GraphSimNode

    One node in the simulation. x/y/vx/vy are written in place by d3-force on every tick, which is why these objects are mutable and reused rather than rebuilt per frame.

    interface GraphSimNode {
        foldedFrom?: string[];
        fx?: number | null;
        fy?: number | null;
        id: string;
        index?: number;
        kind?: string;
        label: string;
        provenance?: {
            conversationId?: string;
            messageId?: string;
            pollId?: string;
            pseudonym?: string;
        };
        statement?: string;
        type: GraphNodeType;
        vx?: number;
        vy?: number;
        x?: number;
        y?: number;
    }

    Hierarchy

    • SimulationNodeDatum
      • GraphSimNode
    Index

    Properties

    foldedFrom?: string[]

    A concept's own labels folded into it once a series graph outgrew its size cap, for the detail panel.

    fx?: number | null

    Node’s fixed x-position (if position was fixed)

    fy?: number | null

    Node’s fixed y-position (if position was fixed)

    id: string

    Unique across all three payload arrays, so one map keyed by id is safe.

    index?: number

    Node’s zero-based index into nodes array. This property is set during the initialization process of a simulation.

    kind?: string

    A contribution's short relationship verb, always present, for the detail panel.

    label: string

    What to draw on the canvas: a concept's label, an origin prompt's text, or — for a contribution — its statement when it has one, since that is the actual content a leaf carries, falling back to its kind for a contribution that is a plain relationship between concepts rather than any one person's account.

    provenance?: {
        conversationId?: string;
        messageId?: string;
        pollId?: string;
        pseudonym?: string;
    }

    Type Declaration

    • OptionalconversationId?: string

      Carried even though the artifact knows its own container, because a topic-scoped graph draws on several conversations.

    • OptionalmessageId?: string

      The specific message this node came from

    • OptionalpollId?: string

      The poll this node was seeded or cited from

    • Optionalpseudonym?: string

      Display name of whoever contributed it

    statement?: string

    A contribution's sentence-long account of the relationship, for the detail panel.

    vx?: number

    Node’s current x-velocity

    vy?: number

    Node’s current y-velocity

    x?: number

    Node’s current x-position

    y?: number

    Node’s current y-position