Saving, sharing and the share card

The draft bar#

Every change you make on the Theme tab is a draft until you say otherwise. The moment a draft exists, a box appears at the bottom right of the window — wherever you are in the app — reading Unsaved theme changes, with one line saying what you can do: Update "Mine", or keep it and save these changes as a new theme, or on a built-in, "Semantix Native" is built-in, so save these changes as a new theme. And always: Unsaved changes are dropped when the app closes.

Three buttons:

Discard — drop the changes; the saved theme comes back exactly as saved.

Update — bake the changes into the theme you're on, in place. Only on a theme of your own; built-in themes can't be overwritten.

Save as new… — a name field appears. Type a name and press Save (or Enter). That captures everything: the palette, your colour overrides, the editor font and syntax theme, your section stylesheets and part edits, the wallpaper. The result is self-contained — it keeps no link to the theme you started from — and it's selected. Names must be unique; a duplicate is refused with A theme with that name already exists.

The chevron folds the box to a small Unsaved pill. There is no close button: closing would throw away the draft, and a box people close to see what's behind it must not do that.

Important

A draft does not survive the app. Close Semantix with the pill showing and the next start opens on the theme as it was last saved. There is no draft recovery.

There is no rename. Save under the new name, then delete the old one.

Deleting#

On the Presets page, under the gallery, the active theme's row carries a bin — Delete this theme — on your own themes only. It doesn't ask for confirmation. Deleting the theme you're wearing drops you back to Semantix Native.

Where themes live#

Themes are stored per user, not per project — with your other global preferences under ~/.semantix/USER/ — so they follow you into every project on this machine. They do not travel to another machine on their own; that's what export is for.

Note

Not everything on the Theme tab is part of a theme. The Glass page — translucency, panel and surface opacity, depth — and the two font sizes are remembered per project, and stay behind when you export.

Export and import#

Three icons sit on the Presets page's title line.

Export writes a <name>.semantix-theme.json file to your Downloads folder and says so — Saved to Downloads ✓. It carries the whole look — palette, editor font, syntax theme, part edits, section code, and the wallpaper, images embedded — and it exports what you're currently looking at, unsaved edits included, so you don't have to save before sharing.

Import takes such a file, adds it as a new theme, and switches to it — Imported "Name" ✓. It never overwrites an existing theme, and importing counts as a save. A file the importer can't read says That file isn't a valid theme beside the icons for a few seconds.

Important

Importing a full theme replaces the deeper layers, including by absence. If the file carries no section code, your current section code is cleared rather than kept — the point being that you get the look as its author made it, not a mixture. Export your own work first if you want it back. There is no preview and no undo; undoing an import means deleting the theme it created.

The middle icon draws a poster of your theme — Card saved to Downloads ✓ — a PNG painted entirely from that theme's own colours, showing the palette as swatches, the accent's hex, and a small mock-up of the IDE wearing it.

The card is for showing, not for installing — it contains no theme data. The picture is what you post; the .json is what someone imports.