Claude 6589bcceee fix(views): make boolean view params work, and retune the prompter
The params editor could not represent a boolean which defaults to true.
Two bugs stacked:

- ParamInput fell back with `isStringBoolean(param) ?? defaultValue`, but
  isStringBoolean answers false for an absent param rather than nothing, so
  the ?? never fired and every switch opened off whatever its option said.
- An unchecked checkbox is absent from the form data rather than present and
  false, so switching one off wrote no param and the parser fell back to the
  default the user was trying to leave.

Either one alone is invisible while every boolean defaults to false, which is
why this surfaced with the teleprompter. Together they made the whole panel
look inert: the switch showed off, the view showed on, and Apply did nothing.

Prompter changes from the review:

- Speed is calibrated against the reading rate rather than picked for feel.
  30 lines per minute was about 300 words per minute, roughly twice a
  broadcast read; the default is now 12, measured at 129 wpm on the default
  column. The ceiling comes down from 200 to 40 so the arrows stay useful.
- Smaller, denser defaults: 40px over 1.3 line height in an 80% column, which
  is 21 lines on a 1080p screen where the old defaults gave 11.
- The reading line is a marker one line tall in the gutter beside the text,
  replacing the rule across the words and the pair of margin arrows. The
  option is a boolean now that there is one style rather than three.
- Space always drives the transport. It was deferring to whichever control
  had focus, so a prompter stopped responding to the pedal after anyone
  touched a button; the overlay drops focus after a pointer press instead.
  Enter still activates a focused control, so the overlay stays keyboard
  operable.
- The help dialog is laid out as the rundown shortcuts panel is, down to the
  Kbd keycaps and the grouping, and no longer explains foot pedals.

Headings stay on the same left rail as the script rather than centred: they
are signposts for the operator, and a second alignment would give the eye
something new to find at every segment change.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Cb8RVPNQ2ETPJxdy4b8CHf
2026-08-18 12:00:25 +00:00
2026-05-28 09:50:20 +02:00
2023-05-18 14:02:22 +02:00
2026-03-08 16:22:12 +01:00
2026-07-01 12:48:40 +02:00
2026-06-11 18:58:00 +02:00
2026-03-08 16:22:12 +01:00
2026-03-08 16:22:12 +01:00
2026-03-08 16:22:12 +01:00
2021-06-12 19:26:37 +02:00
2026-08-09 10:44:13 +02:00
2026-03-08 16:22:12 +01:00
2026-03-08 16:22:12 +01:00

License: GPL v3 GitHub Downloads (all assets, all releases) Docker Pulls NPM Downloads Homebrew Cask Version

Download the latest release

Buy Me A Coffee

... or

Need help?

We do our best to have most topics covered by the documentation. However, if your question is not covered, you are welcome to fill in a bug report in an issue, ask a question in GitHub discussions or hop in the discord server for a chat.

Using Ontime?

Let us know! Ontime improves from the collaboration with its users. We would like to understand how you use Ontime and appreciate your feedback.

Ontime

Ontime is a browser-based application that manages event rundowns, scheduling, and cueing.

With Ontime, you can plan, track your schedule, manage automation and cross-department show information all in one place.

Ontime is made by entertainment and broadcast engineers and used by

  • Conference organisers
  • Touring shows and receiving venues
  • Broadcasters and streamers
  • Theatres and opera houses
  • Houses of worship

Main features

  • Multiplatform: Available as a Cloud service and for Windows, macOS, Linux, or self-hosted via Docker.
  • In any device: Ontime is available to any device with a browser, eg: tablets, mobile phones, laptops, signage, media servers...
  • Team Collaboration: Dedicated views for directors, operators, backstage, and signage.
  • Real-Time Updates: Manage and communicate runtime delays effortlessly.
  • Automatable: Ontime can be fully or partially controlled by an operator, or run standalone with the system clock
  • Flexible Integrations: Use one of the APIs provided (OSC, HTTP, Websocket) or the available Companion module to integrate into your workflow (vMix, disguise, Qlab, OBS)

... and a lot more ...

For live environments

Ontime is designed for use in live environments.
This guides the application into being flexible and efficiently integrating into different workflows.

For teams

All information added in Ontime is shared with the production team and other software / hardware in your workflow.
Ontime also improves team collaboration with dedicated views for cuesheets and operators, and for public and production signage.

Simple infrastructure

All the data is distributed over the network, making its distribution and infrastructure flexible and cheap.
With the availability of the docker image, you can also leverage IT infrastructure to make Ontime available online for your team and clients.

Ontime is made by video engineers and entertainment technicians.

App Window

Views

Read the docs to learn more

Using Ontime

Getting started

The easiest way to start with Ontime is by leveraging our Cloud service.
This will give you immediate access to running instances of Ontime which are available to share with anyone with an internet connection.

Alternatively, you can run Ontime locally for free by downloading the latest release for your platform or using the docker image, available at Docker Hub

Once installed and running, any device that shares the same network as Ontime will have access to Ontime.

More information is available in our docs

Continued development

Ontime is under active development. We continue adding and improving features in collaboration with users.

Have an idea? Reach out via email or open an issue

Issues

We use Github's issue tracking for bug reporting and feature requests.
Found a bug? Open an issue.

Contributing

Looking to contribute? All types of help are appreciated, from coding to testing and feature specification.

If you are a developer and would like to contribute with code, please open an issue to discuss before opening a Pull Request.

Information about the project setup can be found in the development documentation

License

This project is licensed under the terms of the GNU GPL v3

Sponsor

You can help the development of this project or say thank you with a one time donation.
See the terms of donations.


Buy Me A Coffee

S
Description
Free, open-source time keeping for live events
Readme 38 MiB
Latest
2026-06-07 11:53:25 +00:00
Languages
TypeScript 92.5%
SCSS 6.1%
JavaScript 1%
HTML 0.4%