-
Notifications
You must be signed in to change notification settings - Fork 0
Files and Projects
A project is a .valendo file that you choose to write, with Ctrl+S. It holds the whole programme: every tab, its text, appearance, markers, chapters, and the cards with their images embedded. It is what you carry to another machine or hand to a colleague.
The session is autosaved continuously into workspace.json, without you asking. It exists so a power cut or a stray Alt+F4 does not cost you the script.
They are not the same, and the difference matters: closing the app after editing without saving keeps your work in the session, but the .valendo on disk is still the old one. Valendo asks before letting that happen.
Valendo does not restore the last script by itself. The screen starts blank and the welcome screen offers Pick up where I left off — a deliberate click.
The reason is not tidiness. Opening a teleprompter in a studio that is not yours, or with the machine already mirrored to a wall, used to put the previous show on screen in front of whoever was in the room. A script is a client's material.
Recent projects appear as chips on that screen, and clear empties the list — the names of the files carry information too.
The last five projects opened or saved. Available in two places:
- The chips on the welcome screen.
- The small arrow beside the open button in the PROJECT group.
The list is per machine and never travels inside a .valendo — sending a project to a colleague would otherwise send them a map of your disk. Files that have been moved or deleted drop off the list on their own, because a shortcut that opens an error is worse than no shortcut.
txt, md, docx and pdf.
The text is cleaned before it becomes a script:
- a word hyphenated at a line break is rejoined
- a line that was only a page break is merged back
- repeated headers and page numbers are dropped
- quotes are straightened
- legacy encodings are detected, so an old Windows-1252
.txtdoes not turn into a soup of diamonds
In PDFs the text is rebuilt from the coordinates of the fragments — two-column layouts included — and a sentence that crosses a page break comes back whole. A scanned PDF is flagged as such; OCR is the next milestone.
The script of the active tab, as txt, md, docx or pdf. Chapters become headings, stage directions stay in brackets.
Windows: %APPDATA%\Valendo
| File or folder | What it holds |
|---|---|
workspace.json |
The session, restored only when you ask |
history/<tabId>.jsonl |
Infinite undo, kept across sessions |
recentes.json |
The recent projects list |
defaults.json |
How a new tab is born — Save as default writes this |
ui.json |
Interface scale |
keymap.json |
Remapped keys |
cartoes/ |
Card artwork, copied in |
convertidos/ |
Playable copies of videos that needed conversion |
problemas.log |
Storage failures, if any ever happened |
Window size and position, panel widths, thumbnail size, interface scale, the editor's type size and its ALL CAPS switch are all preferences of this machine. They are stripped from the .valendo on the way out.
A project opened on a colleague's console does not resize their window or move their panels. What travels is the programme; what stays is the furniture.
If Valendo cannot read workspace.json, it does not silently start over — it keeps the unreadable file under another name and tells you where it went. If it cannot write, a red strip stays on screen until it can, because a teleprompter that stops saving without saying so is worse than one that will not open.