Rename internal Alchemy names/settings to Slipstream (hard fork) #126

Open
opened 2026-09-27 19:58:34 +00:00 by backspace119 · 0 comments
Owner

Slipstream is now a hard fork of Alchemy. We never intend to upstream, and will only cherry-pick individual upstream changes we want. The user-facing branding is done (product name, channel, binaries, data dir, logs, icons, links). The internal names still say Alchemy; they were deliberately kept during the first rename. Migrate them too.

Scope

  • Settings keys: Alchemy* → Slipstream* in settings.xml/settings_alchemy.xml and every gSavedSettings / LLCachedControl / XUI control_name / menu parameter reference.
    • Needs a migration: on load, copy any saved Alchemy* value to its new key, so users keep their settings (see the existing first-run data-dir copy in LLAppViewer).
    • Keep reading the old names for a release or two.
  • Source files and classes: al*.cpp/h (alchatbar, altpscamera, alviewermenu, …), AL* class names, ALToolTPS, etc. → a Slipstream prefix. Rename with git mv so history follows.
  • Env vars: ALCHEMY_* → SLIPSTREAM_* (e.g. ALCHEMY_AFFINITY, ALCHEMY_NO_AFFINITY, ALCHEMY_VK_VALIDATION). Accept the old names for a while.
  • XUI names:
    • the alchemy skin folder;
    • Alchemy* texture names (AlchemyRelease128 …);
    • floater/panel names that embed "alchemy";
    • the settings_alchemy.xml file name.
  • Build: USE_* / CMake options, LL_* defines that carry Alchemy naming, the AlchemyViewer 3p repo references where we vendor our own packages later (the branding package is no longer used for icons).
  • Logs / diagnostics: tag names and comments that say Alchemy.
  • Keep: license and copyright attribution ("based on Alchemy, © Alchemy Development Group"), the About credits, and doc/contributions.txt history.

Notes

  • This is a big mechanical change. Do it in one branch with scripted renames plus the settings migration, and build both platforms.
  • It makes future cherry-picks from upstream Alchemy need path/name translation. Accepted, since we're hard-forking.
Slipstream is now a **hard fork** of Alchemy. We never intend to upstream, and will only cherry-pick individual upstream changes we want. The user-facing branding is done (product name, channel, binaries, data dir, logs, icons, links). The *internal* names still say Alchemy; they were deliberately kept during the first rename. Migrate them too. ### Scope - **Settings keys:** `Alchemy*` → `Slipstream*` in `settings.xml`/`settings_alchemy.xml` and every `gSavedSettings` / `LLCachedControl` / XUI `control_name` / menu `parameter` reference. - **Needs a migration:** on load, copy any saved `Alchemy*` value to its new key, so users keep their settings (see the existing first-run data-dir copy in `LLAppViewer`). - Keep reading the old names for a release or two. - **Source files and classes:** `al*.cpp/h` (`alchatbar`, `altpscamera`, `alviewermenu`, …), `AL*` class names, `ALToolTPS`, etc. → a Slipstream prefix. Rename with `git mv` so history follows. - **Env vars:** `ALCHEMY_*` → `SLIPSTREAM_*` (e.g. `ALCHEMY_AFFINITY`, `ALCHEMY_NO_AFFINITY`, `ALCHEMY_VK_VALIDATION`). Accept the old names for a while. - **XUI names:** - the `alchemy` skin folder; - `Alchemy*` texture names (`AlchemyRelease128` …); - floater/panel names that embed "alchemy"; - the `settings_alchemy.xml` file name. - **Build:** `USE_*` / CMake options, `LL_*` defines that carry Alchemy naming, the `AlchemyViewer` 3p repo references where we vendor our own packages later (the `branding` package is no longer used for icons). - **Logs / diagnostics:** tag names and comments that say Alchemy. - **Keep:** license and copyright attribution ("based on Alchemy, © Alchemy Development Group"), the About credits, and `doc/contributions.txt` history. ### Notes - This is a big mechanical change. Do it in one branch with scripted renames plus the settings migration, and build both platforms. - It makes future cherry-picks from upstream Alchemy need path/name translation. Accepted, since we're hard-forking.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
backspace119/Slipstream#126
No description provided.