Manual
The Neuridion manual
Everything, honestly: the book explains how the product thinks, the reference lists every command — each with its signature, and worked examples that are kept true by tests. Use the search above; it knows every heading and every command.
The book
From an empty window to a running application — one sitting.
Schema & dataTables, fields, relationships, computed columns — and what money is.
Forms & windowsThe canvas, the objects, styles, tabs — and the events between them.
ListsOne list everywhere — row actions, editable cells, footers, reordering.
Scripts & eventsWhere code runs, what each event means, and what a script may touch.
Reports & printingThe report editor, form letters, labels — and printing from a list.
Import & exportCSV, JSON, XML — mapping, key fields, and running it again next month.
Backups & restoreAutomatic copies, packages, passwords — and what a restore really does.
Building & shippingTest and release builds, signing, notarization — and the licence.
Client / ServerOne server, a client on every desk — pairing, locks, backups, updates.
Record lockingTwo people, one record — how it is handled automatically, and by hand from a script.
Performance — how it is fastInterpreted and compiled at once — the three compilers you never run, and the measured numbers.
DebuggingBreakpoints, stepping, the query log — on real data.
Limits — the honest chapterWhat Neuridion deliberately does not do, and why.
The reference
The API, group by group
Every command lives in a group — the only free names are the data
objects database, record, form,
event, and log. English, camelCase, no abbreviations, and
everything is synchronous: a script reads top to bottom, and a call has its answer on
the next line.
database, records & queries
The data itself. database.customers is a table, a query is a chain that stays lazy until something asks, and a record is an object — the same row is always the same object. The badges say what each command means for the wire in a Client/Server pair — green: only an answer returns; red: rows or bytes travel — with measured times (localhost; an office LAN adds ~0.3–3 ms per round trip). Single-user applications have no wire and pay none of it.
form & event
Inside a form script, form is this window — its objects by name, its record — and event says what just happened. Both exist only where they mean something: a menu script has no form.
forms
Windows in general — the plural is the group, the singular (form) is the window you are standing in.
messages
Talking to the person at the keyboard — dialogs, sounds, progress. Everything here blocks the script until it is answered, which is what a synchronous API means.
application
The application itself — what it is called, which version it is, and the one way to end it.
security
Passwords and the keychain. Deliberately small: who may do what is your application's question — these are the tools to answer it with.
reports
Printing goes through reports — the ones you designed, so there is one printing engine, not two.
files
Folders, dialogs, reading and writing text — and the permissions macOS puts between an application and the disk.
xml
XML in and out, as a tree of plain objects.
language
The Mac reads for you — on the customer's own machine, nothing leaves it.
ai
A model answers — Apple Intelligence on the Mac by default, or a provider you configure. Synchronous like everything else.
system
The machine and the person at it — language, appearance, clipboard.
log
The console, and the application's log file.