Follow-up to #3, which did the cosmetic rebrand only. These are the load-bearing names still carrying the old brand.
In scope
| Name |
Where |
nextui.elf |
makefile, .vscode/launch.json, each platform's MinUI.pak/launch.sh (desktop, tg5040, tg5050) |
/tmp/nextui_exec |
MinUI.pak/launch.sh, all three platforms |
nextui.txt (log) |
MinUI.pak/launch.sh |
NextUISettings |
config.c, config.h, palette.h — 6 references, trivial |
NextUI-$(RELEASE_TIME) |
release zip name, top-level makefile |
workspace/all/nextui/ |
source directory; touches workspace/makefile and the build rules |
Why it wasn't done in #3
The binary rename runs through the boot chain — MinUI.pak/launch.sh is what execs the UI. Getting it wrong means a device that boots to a black screen, and it can't be verified without hardware. Contained (5 files reference nextui.elf), just wants a real device on the other end.
Not in scope — do not rename
MinUI.pak, MinUI.zip, minuisettings.txt, .userdata/shared/.minui/.
These are MinUI heritage rather than NextUI branding, and existing installs depend on them: renaming orphans every user's settings, saves, recents and favorites, and breaks the updater, which ships MinUI.zip by name. If they're ever renamed it needs a migration that reads the old locations and moves them.
Suggested order
NextUISettings and the release zip name — no runtime riskworkspace/all/nextui/ and the build rulesnextui.elf, /tmp/nextui_exec, log filename — with a device to test the boot
Follow-up to #3, which did the cosmetic rebrand only. These are the load-bearing names still carrying the old brand.
In scope
nextui.elfmakefile,.vscode/launch.json, each platform'sMinUI.pak/launch.sh(desktop, tg5040, tg5050)/tmp/nextui_execMinUI.pak/launch.sh, all three platformsnextui.txt(log)MinUI.pak/launch.shNextUISettingsconfig.c,config.h,palette.h— 6 references, trivialNextUI-$(RELEASE_TIME)makefileworkspace/all/nextui/workspace/makefileand the build rulesWhy it wasn't done in #3
The binary rename runs through the boot chain —
MinUI.pak/launch.shis what execs the UI. Getting it wrong means a device that boots to a black screen, and it can't be verified without hardware. Contained (5 files referencenextui.elf), just wants a real device on the other end.Not in scope — do not rename
MinUI.pak,MinUI.zip,minuisettings.txt,.userdata/shared/.minui/.These are MinUI heritage rather than NextUI branding, and existing installs depend on them: renaming orphans every user's settings, saves, recents and favorites, and breaks the updater, which ships
MinUI.zipby name. If they're ever renamed it needs a migration that reads the old locations and moves them.Suggested order
NextUISettingsand the release zip name — no runtime riskworkspace/all/nextui/and the build rulesnextui.elf,/tmp/nextui_exec, log filename — with a device to test the boot