ov-graph

src/ov-graph.js

LIFTED FROM demo/graph.html

Attributes

None.

Properties

None that can be set. See the read-only properties below.

READ-ONLY PROPERTIES

links

Events

None.

Using it

import 'overscan'
import 'overscan/overscan.css'

<ov-graph>
  <ov-node
    id="a"
    label="SENSOR"
    x="14"
    y="16"
  >
    <ov-socket
      dir="out"
      name="level"
      type="scalar"
    >
    </ov-socket>
  </ov-node>
  <ov-node
    id="b"
    label="MIX"
    x="190"
    y="72"
  >
    <ov-socket
      dir="in"
      name="a"
      type="scalar"
    >
    </ov-socket>
  </ov-node>
  <ov-link
    from="a.level"
    to="b.a"
  >
  </ov-link>
</ov-graph>

import { OvGraph } from 'overscan/react'

<OvGraph />

import { OvGraph } from 'overscan/vue'

<OvGraph />

import OvGraph from 'overscan/svelte/OvGraph.svelte'

<OvGraph />

The CSS is a separate import in every framework. A single element can be imported on its own instead of the whole kit: import 'overscan/src/ov-chart.js'

A reading is set as a PROPERTY, never an attribute. An attribute is a string, so an array cannot survive one and a null arrives as the word "null", which the protocol would read as a value rather than a dropout.

Every ov: event is bound with addEventListener. The colon has no declarative spelling in Svelte 5, where the on: directive is gone and "onov:commit" is not an identifier, nor in JSX. Vue can bind it.

The wrapper applies attributes ITSELF and hands the framework nothing but a ref. All three frameworks set a prop as a property when the name exists on the element, and this kit has 77 getter-only properties across 43 elements. Assigning one throws, and in React it does not degrade: the whole tree fails to render. 13 elements have a getter-only name that is also a real attribute (at, bearing, digits, duration, floor, fov, fresh, hold, lat, lon, period, pitch, range, ring, rings, span, step, sweep, sweeps, traces, value), which are the ones a reader would naturally pass in markup.