ArchitectureA supervised JVM-class runtime — OLTP on seven engines, OLAP on three. AI-native, MCP-native, observable as plain SQL.Read the architecture
Está viendo la edición Perú. Está viendo la edición Colombia. You're viewing the Pakistan edition. Cambiar a la edición global →Cambiar a la edición global →Switch to the global edition →
UIProduct Release1 min read

RF terminals for the warehouse: one form engine on VT100 scanners and browsers

A thin client for handheld scanners downloads menus, forms and events from the dictionary and renders them on a VT100 screen or in a Carbon web view from one form engine, in eight languages.

A warehouse runs on handheld scanners with small screens, a numeric keypad and a VT100 emulator, and the same forms must work on a browser at the desk. This release makes one form engine serve both.

One engine, two renderings

  • Downloaded, not installed Menus, forms and JavaScript events come from the dictionary over a REST API, with GraalVM running the scripts.
  • VT100 A rich-row field list, combo dropdowns, checkbox toggles, group and hide conditions, and inline errors in red, on a terminal.
  • Web The web view moved to IBM Carbon in its dark theme.
  • Values kept A shared form store keeps entered values across close and reopen in both views, and a form-based login returns session globals such as the operator's warehouse.

Proven and packaged

  • Eight languages in both layers, and timestamps rendered in the terminal's zone when the server sits in another.
  • Tested against a mock The mock backend is an in-memory SQLite rebuilt from a single dataset on every start; 287 tests pass unchanged, 226 test methods over some 53,000 lines.
  • Credential-free distribution A tarball with a first-run wizard that pings the server and encrypts the password.

The platform's user interface story usually means a browser. On the warehouse floor it means this.

On the platformUI ExperiencePlatform

All posts