Tools
The Tools page in the control centre holds three things that work on your files: a drawing board, publishing a folder to GitHub, and the external editor choice. Long jobs show their progress in a shared progress card.
- Live check: runs the app against real voices, Ollama, the dish catalogue, a forge server and the Minecraft jar.
- Drawing and annotation
- Publishing to GitHub, GitLab and Gitea
- External editor
- Progress and recovery
- Local history for scripts and the commit message
- Base64 beside the file
Nothing on this page stores a password or token. A token pasted to create a repository on GitLab or Gitea is used once and cleared. Drawings stay on this computer.
Articles
Live check
the parts that only mean something against the real thing. It uses a throwaway data folder, so the real settings are
Read itDrawing and annotation
Open it from Tools: a blank board, an image file, or the newest picture in clipboard history. Annotating never changes the original image.
Read itPublishing to GitHub, GitLab and Gitea
Publishes a folder (or the IP history repository when it is set up) in five visible steps: check tools, prepare the repository, commit, choose the remote, upload.
Read itExternal editor
Detects Visual Studio Code (per-user, machine, Insiders, and code.cmd on PATH), Notepad++, the system default and one custom program. The preferred editor is a setting (default: automatic, which…
Read itProgress and recovery
Used by publishing. Status: compile-checked only.
Read itLocal history for scripts and the commit message
Every save of a shortcut script keeps a versioned copy, and so does every save of the default commit message template. Nothing is uploaded.
Read itBase64 beside the file
A card on the Tools page writes a file's Base64 text next to it, and turns that text back into the file.
Read it