ov-annunciator

src/ov-annunciator.js

LIFTED FROM demo/annunciator.html

Attributes

Properties

Events

Using it

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

<ov-annunciator
  tiles="FUEL LOW,HYD PRESS,CABIN ALT,O2 FLOW"
  conditions="FUEL LOW=off, HYD PRESS=on, CABIN ALT=on, CABIN ALT=off, O2 FLOW=null"
  style="--ov-annunciator-cols:2;--ov-annunciator-tile-w:11ch"
></ov-annunciator>

import { OvAnnunciator } from 'overscan/react'

<OvAnnunciator
  tiles="FUEL LOW,HYD PRESS,CABIN ALT,O2 FLOW"
  conditions={data}
  onAcknowledge={handler}
  onAnnunciate={handler}
  onShelve={handler}
/>

import { OvAnnunciator } from 'overscan/vue'

<OvAnnunciator
  tiles="FUEL LOW,HYD PRESS,CABIN ALT,O2 FLOW"
  :conditions="data"
  @acknowledge="handler"
  @annunciate="handler"
  @shelve="handler"
/>

import OvAnnunciator from 'overscan/svelte/OvAnnunciator.svelte'

<OvAnnunciator
  tiles="FUEL LOW,HYD PRESS,CABIN ALT,O2 FLOW"
  conditions={data}
  onacknowledge={handler}
  onannunciate={handler}
  onshelve={handler}
/>

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.