QuartzControl 1.0.2

A bugfix release: four things that got in the way in 1.0.1, and what a review of the fixes turned up
around them. Feedback is welcome — an issue is the easiest way.

Coming from 1.0.1

Nothing to do. One thing worth a look: if you ever cleared a plugin option in 1.0.1 — the layout
box's html, say — the configuration may still hold an empty value for it, which the plugin reads
as set (a layout box then shows nothing instead of reading its file). Such a field now says
set to empty; Reset next to it removes the option.

What changed since 1.0.1

Plugins

• Clearing an option field removes the option from the configuration instead of writing an
  empty value; the plugin uses its default again. For the plugins that read "empty" differently from
  "not set" — a heading that should not appear at all — an empty text field offers Set empty.

Styles

• Custom CSS: clicking a variable inserts it at the cursor you placed in the editor, not at the
  end of the file. Without a placed cursor it still goes to the end, never in front of the imports.

Preview & build

• A second dev server no longer needs its ports changed by hand. If a port is in use, the server
  takes the next free one and the console says which. Two exceptions, both refused with a sentence
  instead: a server for the same project that was not started from the app (it would build into the
  same output folder), and a remote dev host (a tunnel forwards exactly these ports).

Git sync

• Pull and push are disabled when there is nothing to sync with — no origin, or no repository
  — and the reason stands next to them, instead of a git error after the click.
• "Could not read" is no longer shown as "not a git repository". A broken index, a folder git
  refuses or a missing git now show what git says, on the Git sync page and in the overview.

The handbook (https://boxi-os.github.io/QuartzControl/) is up to date with this version.

Which file

System	File
macOS, Apple Silicon	QuartzControl-1.0.2-arm64.dmg — or .zip
macOS, Intel	QuartzControl-1.0.2-x64.dmg — or .zip
Linux, x86_64	QuartzControl-1.0.2-x86_64.AppImage or quartzcontrol_1.0.2_amd64.deb
Linux, arm64	QuartzControl-1.0.2-arm64.AppImage or quartzcontrol_1.0.2_arm64.deb
Flatpak	QuartzControl-1.0.2-x86_64.flatpak or …-aarch64.flatpak

Linux needs glibc 2.34 or newer for the bundled git — Ubuntu 22.04, Debian 12, RHEL 9,
Fedora 35 and later. On an older system the app starts and says it cannot use its own git; a git
from the package manager gets you going. The Flatpak does not raise the question.

Before the first start

macOS. The app is ad-hoc signed and not notarised; there is no Developer ID certificate, so
macOS refuses the first launch. Allow it under System Settings → Privacy & Security → Security →
"Open Anyway", within about an hour of the refused launch. Or clear the quarantine flag:

xattr -dr com.apple.quarantine /Applications/QuartzControl.app

After the update macOS asks again whether this version may use the Keychain — usually twice.
Answer Always Allow both times.

Linux. Make the AppImage executable and run it, or install the deb with
sudo apt install ./quartzcontrol_1.0.2_amd64.deb. For the Flatpak:

flatpak install --user QuartzControl-1.0.2-x86_64.flatpak

--filesystem=home is set, so projects under your home directory work as they are. A content
folder on another drive needs a one-off flatpak override --filesystem=<path>.

What is inside every package

• Node and npm — Electron's own runtime (Node 24.18.1, npm 11.17.0), exposed as three shims on
  the PATH. Nothing to install.
• git 2.53.0 — used only when the machine has none that answers; otherwise the system's own wins.
• The basic template — for creating a project when there is no network.

Known limits

• Not notarised on macOS, as above. No self-update: the start screen reports a newer
  version and links to it. No Windows, deliberately; the reasons are in the README.
• Not started on its own kind of machine: the macOS Intel build (there is no Intel Mac here),
  and Linux with a system git older than 2.38. Both are built; neither was run on such a machine.
• A YAML error in the frontmatter of a single note stops the dev server. That is Quartz; the
  app shows the server as crashed.

Checksums (SHA-256)

7bdf78417456836f5f2d753063026fdb05a225c8f07dfa5018e7c386ede5c1a3  QuartzControl-1.0.2-arm64.dmg
088479e30acd74aee36ec9158341f1ac95f7acbdaef590b887865f8d45e2d091  QuartzControl-1.0.2-arm64.zip
041e35034197f11cb7ab40be7f8e00f27f2b0473d47d6944411cc88ea321ba90  QuartzControl-1.0.2-x64.dmg
ffc74654f02c9396401a6e1639be7c7deb7e22cff628b68e5bffd67cdd9c2738  QuartzControl-1.0.2-x64.zip
507938cb6d80d3c63c5feb66d6eae58a0a53be2b873201e027f4de6da58af05b  QuartzControl-1.0.2-arm64.AppImage
48df02ba558e3e6c36fc9cb1a7d757da0e1a486163f28b2a70ff7d6c8652f2af  QuartzControl-1.0.2-x86_64.AppImage
edb55e8f941dd74d0f843776489c1ff5681d8c66e310eefc4bf362bf310fb318  quartzcontrol_1.0.2_arm64.deb
c38f663e50e57047bb00debf90fc854b81393cb4c30eae4b3c1939ba77701519  quartzcontrol_1.0.2_amd64.deb
6b09b87e1618a5b1b88837cac1757cd7a13bcf3685bbb193536452e97f21b41d  QuartzControl-1.0.2-aarch64.flatpak
8fbfc34abadbb2f6836e8c7abc348dce3843b091dd8c25eecd350ed89cb97346  QuartzControl-1.0.2-x86_64.flatpak