Make SaraTag installable through SaraSuite.

This commit is contained in:
sarah committed 2026-10-08 19:06:24 +02:00
1 parent 845d6c6ee6
commit c0f3d4cbfa
6 files changed
+102 -7

No files matched your search

+11 -4
View File
@@ -40,15 +40,22 @@ appearance and export/import, SaraTag's own settings, and `SaraTagConf.toml`'s B
| --- | --- |
| `~/.config/SaraSuite/Config.toml` | shared SaraSuite settings (theme, font, title bar) |
| `~/.config/SaraSuite/SaraTag/Config.toml` | SaraTag's own GUI settings |
| `SaraTagConf.toml` | SaraTag's data settings (portable, next to the program) |
| `SaraTagConf.toml` | SaraTag's data settings |
| `.SaraTagRecords.toml` | Records and Libraries |
| `.SaraTagHistory.toml` | where each Record/Library was left, recent files, updater runs |
| `Lexicons/` | Lexicons (not in git) |
| `Lexicons/` | Lexicons |
The last four live in SaraTag's data folder, which `.saratag/Core.py` picks in this order:
`$SARATAG_DATA_DIR`; `DataDir` in `.saratag/Location.toml` (installed by SaraSuite, pointing at
`~/.config/SaraSuite/SaraTag/`); otherwise the program folder itself, so a plain copy stays portable.
Missing files are created on start. None of them are in git.
## Running
`python3 -m venv .venv && .venv/bin/pip install -r requirements.txt`, then `Packaging/Launch.sh`
(or `.venv/bin/python Main.py`; `SaraTag.py` still works too).
- SaraSuite: install SaraTag from it. `Packaging/SaraSuite/` is the manifest (`Manifest.toml` + `Templates/`),
kept in sync with SaraSuite's `Programs/SaraTag/`.
- From source: `python3 -m venv .venv && .venv/bin/pip install -r requirements.txt`, then `Packaging/Launch.sh`
(or `.venv/bin/python Main.py`; `SaraTag.py` still works too).
## Files