Manual · The book

# Getting started

From an empty window to a running application — one sitting.

Where it starts. The recent projects on the right are the ones you had open last.

Neuridion builds database applications the way you sketch them: draw the schema, design the windows, write JavaScript only where a rule is genuinely yours — and press Run. This chapter walks the whole road once, quickly, so everything after it has a picture to hang on.

## 1 · A new project

File ▸ New offers three doors: an empty project, an example with its data (Harbour Supply — seven tables, eleven windows, worth taking apart), or describe your business and let the assistant lay out a first draft. For this walk, start empty.

Three doors — and the panel underneath says what you will be looking at the moment the window opens.
The middle door hands over a finished project with its data — it is inside the application, so it works on a train, and what you get is listed before you choose.

## 2 · Draw the schema

The Schema tab is a canvas. Press `＋` to add a table, double-click a field to open its editor — type, required, unique, decimals. Drag from one table to another to create a relationship; Neuridion adds the foreign key and the delete rule for you. Money is its own type (Amount, whole cents — never floating point), files and images are columns like any other.

## 3 · Windows, without writing them

Right-click a table ▸ Give me something to work with and answer two questions: which windows, which fields. You get a list window and a record window that already work — search, sort, print, import and export included, none of it written by hand. Everything the generator made is yours to rearrange on the form canvas.

## 4 · Run

Press ▶︎. Your application opens against a development database that lives beside the project. Type into a field and leave it — it is already saved. Neuridion has no Save button: leaving a field writes it, closing a window asks only when a record cannot be written.

## 5 · A line of JavaScript

Select a button on a form, open its `onClick` in the editor and write:

    // Count the customer's invoices and say so.
    const paid = form.record.invoices.where("isPaid", "=", true).count();
    messages.alert(paid + " invoices are paid.");

The editor completes `database`, your tables and your fields from the schema, underlines names that do not exist, and ⌘-click jumps to a definition. Every command in this manual works exactly the same way in any event script.

## 6 · Build

When it is worth handing to somebody: press Build. Seconds later there is a standalone `.app` — no runtime to install, nothing to configure, and royalty-free: what you build costs your customers nothing, ever. A release build signs and notarizes with your own Apple Developer ID; a test build runs on your Mac without one.