inoGUI — the editor¶
inoGUI is the desktop editor. It is where a project is built: the tags, the screens, the control logic, the devices on every bus and the board it will all run on. It compiles that project into one package and sends it to a panel running inoCORE.
This section is an outline
The pages under it are being written. What each one will cover is stated at the top of it, so the shape of the section is fixed even where the words are not.
What is here¶
| Page | What it will cover |
|---|---|
| Working with a project | The project tree, the page for each node, tags, screens and diagrams. |
| Catalogues | Boards, devices and peripheral chips; what a signed catalogue means. |
| Deploying | Writing the runtime once, then sending a project package over and over. |
What the editor is for¶
- One project, one file. Visualisation, logic, tags and bus configuration live together and are versioned together.
- What you draw is what appears. The canvas is drawn by the same renderer the panel uses, so the fonts, colours and rounding on your screen are the ones on the glass.
- Checked against real hardware. Before anything is deployed, the project is validated against the chosen board — see limits.
- Simulation without a panel. Logic and rendering both build for the PC, so a project can be exercised on the desk.
Licence levels¶
What the editor lets you do depends on the licence — see licensing. The editing range is the same at every level; what changes is what may be compiled and deployed.