Skip to content

Live examples ​

Each example is a whole page a reader could copy, with choices that rewrite it and the page itself running under the code. They sit on the page that covers their subject.

The form ​

ExampleShowsOn
A form on a pageLocale, mode, frame, drafts, data sources, messages, and the server's reply as a receipt or as errorsThe form on your page
A slow serverThe form locked and saying it is submitting while a delivery runs, a timeout, then the receiptSubmissions and replies
Header and footerParts the page adds, parts the form's author composed, or both: logo, title, instructions, language switcherLook and chrome
Parts left outfeatures on the form and on the builderLeaving parts out
Rules of your ownRules run at submit in the sandbox, the data the page hands them, their messages and the run logValidation and the sandbox
A journeyOne form with three journeys: a picker, page changes, a deep link, a draft resumed after a reloadJourneys
A journey page the service checksA page checked through validate-url, and the delivery judged the same wayJourneys
Bootstrap with your own CSSThe Bootstrap binding over Bootstrap's stylesheet and a brand sheet of the site's ownBootstrap with your own CSS
A form in an iframeA host page and the page it frames, sizing and reporting through postMessageIn an iframe
Signing with a hardware tokenThe page wired to the local signing agent; it reports the agent as unreachable when none runsSigning

Languages ​

ExampleShowsOn
A form in two languageslocale negotiated or auto, the form's own switcher, setLocaleLanguages
Translations from the pagetranslations, texts with plural keys and messages meeting the form's own wording, and which winsLanguages
Choices in more than one languageA source told the locale, one that sends every language, and an endpoint read with ?locale=Languages
Language changes at SaveThe languages removed or renamed since the last save, handed to the page's SaveLanguages
The builder's own wordstextCatalog and textLocale rewording the builder's interfaceLanguages

The builder ​

ExampleShowsOn
The builder in a boxSizing, the file actions, the page's own Save on the bar, and every edit reportedEmbedding the builder
Builder and form togetherOne listener hands each edit to a form beside the builderEmbedding the builder
Save with a revision checkfileActions.save, Ctrl/Cmd+S, the unsaved cue, and a stale save refusedEmbedding the builder
A component type of your ownA star rating on the form or the palette, as componentDefinitions or as a pluginComponents of your own
Font Awesome iconsThe builder's icons from the Font Awesome plugin, against its ownCustomising the builder
An icon set of your ownAn icon set written in the pageCustomising the builder
Form testsThe builder opened on a form that carries its scenarios, the Tests panel running themTesting a form

The server ​

Each of these shows the page running against a stand-in, and the endpoint in Python, Java, C# and Node.js.

ExampleShowsOn
Validate on the serverThe endpoint reruns the sandbox program and answers with the same codesExample: validate
Render a PDF on the serverThe endpoint validates, renders the record and answers with the PDFExample: render a PDF
Fill a PDF on the serverThe endpoint writes the answers into a template it keepsExample: fill a PDF
Sign a PDF on the serverThe endpoint seals the PDF with its own certificate, and a second one verifies itExample: sign a PDF

Components for React, Vue and Angular are on React, Vue and Angular. Those are code to copy, not run here.

How they run ​

The result is the code above it, loaded into a frame. Nothing else is wired to it. Two things stand in for a site of your own:

  • The bundle folder, written as /datum/ in the code, is this site's copy.
  • Requests to /forms/ and /api/ are answered by the example in place of a server, and so are the example's own files, such as a stylesheet on a tab beside the page. Where an example has a Server reply choice, that choice is what the stand-in answers. The server examples' stand-in runs the same sandbox and PDF programs a server would.

The log under each result lists the events the element dispatched, what the page wrote to the console and each request it made to the stand-in. A long entry opens to show the whole of it.

MIT licence. Your forms, your data, your keys.