Skip to content

Ev cleanup retire vsettings - #296

Merged
evertvorster merged 9 commits into
masterfrom
ev-cleanup-retire-vsettings
Oct 5, 2026
Merged

evertvorster merged 9 commits into
masterfrom
ev-cleanup-retire-vsettings

Conversation

@evertvorster

@evertvorster evertvorster commented Sep 19, 2026 •

Copy link
Copy Markdown
Contributor

You all knew this was coming sometime.

This PR retires all other settings and associated old stuff that is not needed anymore.

Please answer the following:

Code Changes:

Issues:

  • Please list any related issues
    • Settings app has been superceded.

Purpose:

  • What is this pull request trying to do?
    • Clean up a little
  • What release is this for?
    • 0.11
  • Is there a project or milestone we should apply this to?
    • 0.11

The in-game config screen (Alt+C) now owns settings editing, reading and
writing the split JSON config directly, so the standalone Kivy app is
superseded. Remove it and everything that only existed to launch or
configure it:

- python/settings_app/ (the app itself)
- vega-settings (launcher script)
- vegasettings.desktop + vegastrike_settings.png (its menu entry + icon)
- setup.config (config for the legacy vscsetup utility)
- vsinstall.sh (pre-0.10 installer that launched vegasettings)

and drop their CMake install rules.
The engine no longer parses vegastrike.config; it reads the split JSON
config (config.json, bindings.json, theme.json, engine.json) from the
data directory plus the user overlay. Remove the file and its CMake
install rule, drop the dead settings_app block from config.json (only
the removed Kivy app ever wrote it), and update the readme's control
instructions to describe the in-game settings screen and bindings.json.
Legacy Python 2 CGI server that rewrote vegastrike.config for account
registration. The config XML is gone and the server has not been used in
years; drop it and its CMake install rule.
@evertvorster
evertvorster requested review from BenjamenMeyer, royfalk and stephengtuggy and removed request for stephengtuggy September 19, 2026 12:21
Comment thread documentation/readme.txt Outdated
Comment thread CMakeLists.txt Outdated
…settings

# Conflicts:
#	python/settings_app/templates/advanced_template.json
Multiplayer is not supported at this time outside the 0.5 Legacy edition,
so remove the ALPHA Online Multiplayer Mode section (LAN/Deathmatch and
MMO style play), its Contents entry, the stale New Features bullet, and
renumber the License section.

Addresses stephengtuggy's and BenjamenMeyer's review comments on #296.
Addresses stephengtuggy's review comment on #296.
…settings

# Conflicts:
#	python/settings_app/templates/advanced_template.json

@royfalk royfalk left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems pretty straightforward to me.
One nitpick comment.
Ship it!

Comment thread CMakeLists.txt

@stephengtuggy stephengtuggy left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

He is the project lead, alongside the other authors already listed.
evertvorster added a commit that referenced this pull request Oct 2, 2026
Multiplayer is not supported at this time outside the 0.5 Legacy edition,
so remove the ALPHA Online Multiplayer Mode section (LAN/Deathmatch and
MMO style play), its Contents entry, the stale New Features bullet, and
renumber the License section.

Addresses stephengtuggy's and BenjamenMeyer's review comments on #296.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, is this the file that the config auto-generation used as a source? As such, do we want to keep it?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If it is the file I'm thinking of, it could potentially be used both to auto-generate additional settings UI elements in the new config screen, and as a source of truth for what all the available settings are, along with their default values.

@evertvorster
evertvorster merged commit 8b9676c into master Oct 5, 2026
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants