Skip to content

QuartzControl 1.0.1

Choose a tag to compare

View all tags
@boxi-os boxi-os released this 28 Sep 09:40
· 361 commits to main since this release
v1.0.1
1653dc0

A bugfix release: six things that went wrong in 1.0.0, found in daily use, and two that turned up
while fixing them. Feedback is welcome — an issue is the easiest way.

Coming from 1.0.0

Nothing to do. If you build a site with Google fonts served locally from one of the templates,
the first build after the update tidies the fonts once; the log says what it did (see below).

What changed since 1.0.0

Fonts

  • A family the project brings itself is no longer fetched from Google twice. The templates
    ship Noto Sans and Noto Sans Mono for Latin; with serve locally on, the app fetched the same
    families from Google again and the site carried both. Now it fetches only what the project's own
    font rules do not cover — the other scripts (Cyrillic, Greek, Vietnamese …) still come from
    Google, the Latin part is not duplicated. The build log and the Styles page say what was left
    out and how many font files were removed.

Styles

  • Variables: editing only the light value of a variable that differs between light and dark
    mode keeps its dark value. Until now the dark mode showed the new light value too. The dark
    field shows what really applies in dark mode.
  • Saving no longer loses another save. A font fetch and, say, a variable saved a moment later
    could each undo the other's change in custom.scss. Everything that writes a stylesheet now
    waits for the one before it.
  • A custom.scss that went through a Git merge with a section in it twice is read completely;
    the next save writes one copy.

Layout

  • The layout board sizes its rows to the cards, not to the frame's row heights — a row that is
    0 px high on a phone (a drawer) squeezed its cards on the board.
  • A disabled plugin is marked "Disabled" on the board.

Preview & build

  • The list of servers running on this machine follows when the app starts or stops a server,
    instead of waiting for "Refresh".

Project image

  • After importing a template the app shows its project image in the sidebar, the project image
    card and on the start screen — until now only the dark one appeared, the light one fell back to
    the initial letter.

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.1-arm64.dmg — or .zip
macOS, Intel QuartzControl-1.0.1-x64.dmg — or .zip
Linux, x86_64 QuartzControl-1.0.1-x86_64.AppImage or quartzcontrol_1.0.1_amd64.deb
Linux, arm64 QuartzControl-1.0.1-arm64.AppImage or quartzcontrol_1.0.1_arm64.deb
Flatpak QuartzControl-1.0.1-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.1_amd64.deb. For the Flatpak:

flatpak install --user QuartzControl-1.0.1-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)

b3e3a02d6f388e623a54b5cc6f2ecf41d40c122a58983587c62ee027f817cca8  QuartzControl-1.0.1-arm64.dmg
302183b24b5818f512739e3f6a0591613e0ce92cb7b2911dd28f7e1f2b894283  QuartzControl-1.0.1-arm64.zip
18a7b8761139cff1c46a6f7f6c8875b612010b3c7250e3a05d57c758972e306f  QuartzControl-1.0.1-x64.dmg
82ecec89706bdefa2a47ca80da1524eac4ecc3465bf005555f78d77cc767cd67  QuartzControl-1.0.1-x64.zip
c1672d6c386bec072cf74d550dcd628b755789c23b6860468476c2d649b3a319  QuartzControl-1.0.1-arm64.AppImage
dfb4aef2b0218eba25f42e30607417e92f84e90bb408b662344eba1a6eb64809  QuartzControl-1.0.1-x86_64.AppImage
63446b8553e9a31915349aab8e16720905019fd5c0daddd1b5efda90e404adae  quartzcontrol_1.0.1_arm64.deb
0da9b1debb4359d281442ab2f7d3b5d1cf07d355168e580b676f8b94e04932c3  quartzcontrol_1.0.1_amd64.deb
bc3411c59ceae79ce8cf85107e9f45a9d8451b4e00c456e1959c39996b306008  QuartzControl-1.0.1-aarch64.flatpak
7e78e7817d44a7f6302d42570ee3e72c4b6f239f00fb4f287f6998c74ba189a2  QuartzControl-1.0.1-x86_64.flatpak
Assets 12
Loading