Repository navigation
Veneer 0.3.0
Veneer 0.3.0 adds widgets, output displays and ready-made components for building modern pages from host screens, and supports code page 273 for German and Austrian systems such as PUB400.
What's new
Widgets and displays (#39)
- Input widgets: a switch, a time picker, a masked input, and a lookup with suggestions and a button that sends the host's prompt key.
- Output text shown as a status badge, number, date, yes/no, link, progress bar, or barcode (QR or Code 128), at a position or for every row of a list column.
- Labels, with styles and an optional help tooltip, and images, from the theme, the web or a path filled from screen values. Both are placed, dragged and resized in the designer.
- docs/widgets.md covers adding, configuring and using each one.
Ready-made components (#40)
- Whole-list table, totals, board, calendar, tree, pin map, spool file viewer, barcode scanner, help panel, embedded page and status timeline.
- The bar chart also draws stacked bars, lines, pie, donut and sparklines.
- Components can read a whole list across every page (
ctx.readList()), go back to a row (ctx.openRow()) and read every page of a screen region (ctx.readPages()). - docs/components.md covers installing, placing and using each one.
Code page 273 (Germany/Austria) (#47)
VENEER_CCSID=273is now supported, so umlauts, ß, § and@ [ ] { } \ | ! ~ ^show and are sent correctly. Thanks to @ZodandSons for the report and the patch.- The PUB400 guide now sets it.
Fixes
- Uppercase-only fields keep ß as it is, instead of turning it into SS and lengthening the text.
- Changes to text on the rows a tall display (such as a QR code) covers now go to that text, not to the display.
- Components draw above screen text.
Downloads
| File | What it is |
|---|---|
veneer-0.3.0.zip or veneer-0.3.0.tar.gz |
Ready to run on IBM i or Linux; needs only Node.js. The same files in either format. See deploy/README.md. |
veneer-0.3.0-src.zip or veneer-0.3.0-src.tar.gz |
The source code, for building Veneer yourself (npm ci && npm run build). |
*.sha256 |
Checksums for each archive. |
Unpack the .zip with unzip, which keeps the links inside node_modules. The ready-made components are in examples/components/ of the release archive; copy the ones you want into your components folder.