Overscan instruments

OVERSCANUI KIT

A canvas gauge library measured zero CSS rules and 43 constructor arguments. The library that already looked right was the one that hurt, because a canvas widget is invisible to the cascade and therefore to the theme and both switches. This is the same instrument in SVG: no constructor arguments and no theme object, because everything it looks like already lives in the tokens. The middle dial runs past its scale and pins rather than resting quietly on the limit; the third has no reading and shows no needle, because a needle at zero is a reading. The feed runs each theme's own text arrival, and says how many lines it is not keeping.

demo/instrument.html, from this page

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

<ov-gauge
  source="flux"
  min="0"
  max="100"
  unit="flux"
  ticks="5"
></ov-gauge>

import { OvGauge } from 'overscan/react'

<OvGauge
  source="flux"
  min="0"
  max="100"
  unit="flux"
  ticks="5"
/>

import { OvGauge } from 'overscan/vue'

<OvGauge
  source="flux"
  min="0"
  max="100"
  unit="flux"
  ticks="5"
/>

import OvGauge from 'overscan/svelte/OvGauge.svelte'

<OvGauge
  source="flux"
  min="0"
  max="100"
  unit="flux"
  ticks="5"
/>

terminal

feed

variation: source="press" unit="kPa"

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

<ov-gauge
  source="press"
  min="0"
  max="100"
  unit="kPa"
  ticks="5"
></ov-gauge>

import { OvGauge } from 'overscan/react'

<OvGauge
  source="press"
  min="0"
  max="100"
  unit="kPa"
  ticks="5"
/>

import { OvGauge } from 'overscan/vue'

<OvGauge
  source="press"
  min="0"
  max="100"
  unit="kPa"
  ticks="5"
/>

import OvGauge from 'overscan/svelte/OvGauge.svelte'

<OvGauge
  source="press"
  min="0"
  max="100"
  unit="kPa"
  ticks="5"
/>

industrial

feed

variation: source="dead" unit="aux"

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

<ov-gauge
  source="dead"
  min="0"
  max="100"
  unit="aux"
  ticks="5"
></ov-gauge>

import { OvGauge } from 'overscan/react'

<OvGauge
  source="dead"
  min="0"
  max="100"
  unit="aux"
  ticks="5"
/>

import { OvGauge } from 'overscan/vue'

<OvGauge
  source="dead"
  min="0"
  max="100"
  unit="aux"
  ticks="5"
/>

import OvGauge from 'overscan/svelte/OvGauge.svelte'

<OvGauge
  source="dead"
  min="0"
  max="100"
  unit="aux"
  ticks="5"
/>

cyber

feed

antiseptic

feed

esper

feed

neo

feed

machina

feed

holo

feed

aegis

feed

vector

feed

First out is not first in. With first-out, each line is an event carrying its own time and clock uncertainty, and the log orders by when it happened, not when it arrived. It names a first event only when one is first: two whose windows overlap are a TIE, bracketed together and never put in an order the clocks cannot support, and an event from an unsynchronized clock, or with no time at all, is listed UNORDERED rather than placed. The strip draws each window at its true width, so a tie is two windows overlapping.

a clear first out, which arrived last

two within their clocks: a tie

one clock not synchronized

nothing on a synchronized clock