Imageboop 0.4.0

Changed

• The size controls are now a width, a height, a unit and a checkbox — no mode picker.
  Which field you fill is what happens: width alone resizes by width, height alone by height,
  both together fit inside the two, neither leaves the image alone. A blank field means no
  opinion, and shows greyed what that edge will actually come out at.

  This replaces five menu items that described what the fields were already saying, two of
  which — "Fit within" and "Width" — give identical answers on a landscape photo and so mostly
  created the question they existed to answer.

• Proportional, on by default. Off stretches each edge to its own number, which distorts
  the image. Internally every filled field is just a scale factor, so per cent, pixels, one
  field, two fields, proportional and not are one rule rather than a case each.

• Each thumbnail previews its own result, live. Change a number and every tile updates as
  you type. One aggregate line cannot describe a queue of different shapes: at 2000 wide a
  4284 × 5712 portrait becomes 2000 × 2667 while a 2454 × 1288 landscape becomes 2000 × 1050,
  and quoting the largest image described neither of the others. Images already under the
  target show no arrow at all, since nothing about them will change.

  Changing a setting after a run puts the tiles back to previewing rather than leaving them
  showing what the last run produced under rules that no longer apply.

• Less copy again. The aggregate Output row and the running "N images · N MB" tally are
  gone — the grid was already showing both. What is left is progress while it runs and the
  result when it finishes.

• Process is called Boop.

Fixed

• Dimensions were truncated into nonsense. The thumbnail caption truncated in the middle,
  which is right for a filename and ruinous for a pair of dimensions: "2454 × 1288 → 2000 ×
  1050" rendered as "2454 × 128…00 × 1050", reading as a corrupted number rather than a
  shortened line.
• A zero or negative size in a hand-edited settings file clamped up to 1px and produced a
  one-pixel image. It is now ignored, so nonsense declines to resize rather than destroying the
  picture.

Note

Size settings reset once on first launch: the stored format changed shape and inheriting half
of it would be worse than starting from the defaults.

Imageboop 0.3.0

Changed

• The window is actually translucent now. It was a painted gradient before — Liquid Glass
  only refracts what is behind it inside the window, so the control bar was faithfully
  refracting a static picture and was indistinguishable from a flat panel. The window now
  blends with what is behind it, which is what makes the glass on top of it read as glass.
• Less copy. Gone: the subtitle under "Drop images here", "Results sit next to each
  original", the settings restated under the button, and "No images yet" beside a disabled
  button on a window that already says "Drop images here". What is left after a run is the
  count, the size written, and anything that failed.
• The Output line reports the output. The figure on the right was the total size going in,
  which is already in the status line; it is now the size that came out, with the saving beside
  it.
• Process is called Boop.
• Clear and Boop are the same height. .glass and .glassProminent do not pad their labels
  identically, so the primary button was visibly shorter than the one next to it.
• The size modes explain themselves on hover, with worked examples. "Fit within" and "Width"
  give identical answers on a landscape photo — the width runs out first either way — so the
  two look redundant until you try a portrait, where only Fit within holds both edges under the
  number.

Imageboop 0.2.0

Added

• Help > Send App Feedback…, which files a GitHub issue against the app with your app and
  macOS versions filled in.

  • Send posts it without leaving the app, through Imageboop's own GitHub account, so your
    name is not attached.
  • Open in Browser files it as you instead, needs no setup, and works whether or not you
    trust the above.
  • Use My Own Account… takes a token of your own, kept in your login Keychain, if you would
    rather issues appeared under your name. Yours overrides the shipped one.

  The app carries a token so Send works out of the box. It can create issues on the public
  downloads repository and nothing else — no code, no settings, no other repository — which was
  established by probing the API rather than assumed.

Imageboop 0.1.0

First build. Drop images on a window, pick a size and a format, get them back in a processed
folder beside the originals.

Added

• Bulk resize and convert. Reads everything macOS can open — HEIC, PNG, JPEG, TIFF, GIF,
  WebP, PSD and the RAW formats from the major camera makers — and writes PNG, JPEG, HEIC, TIFF
  or AVIF, or whatever the file already was.
• Five size modes, all preserving aspect ratio: fit within a box, exact width, exact height,
  a percentage, or no resize at all. A px / % menu beside the numbers switches between
  pixels and scaling, and stays in sync with the mode.
• An Output line under the controls showing what the current settings will do — the largest
  image in the queue, before and after — updating as the controls move, and showing the real
  bytes written once a run has finished.
• Folder drops, walked in full, skipping any processed folder found on the way so
  re-dropping a folder does not process its own results.
• Three destinations. The same folder as the originals by default, a named subfolder beside
  them, or one folder of your choosing for everything.
• A queue you can rearrange. Drag a tile and the others shuffle aside to open a gap where
  it would land; let go and it takes that slot. Order is processing order. Hovering a tile
  offers a ✕ and a button that shows the original in Finder, both also on the right-click menu.
• Concurrent processing bounded at cores-minus-one, with per-image progress in the grid and a
  Cancel that never leaves a half-written file.
• Liquid Glass chrome on macOS 26 and later, materials before that.
• Update checking, once a day, as a banner rather than a self-installing updater.

Decisions worth keeping

• Nothing is ever overwritten. A destination that exists gets -1, -2. Running the same
  batch twice at two sizes is an ordinary thing to do, and the version that silently replaced
  the first run's output would be destroying work with no undo. Some files to clean up is a
  worse filename; the alternative is a lost file.
• Output goes beside each original, not into one place. Images dropped from three folders
  produce three processed folders. A central output directory is one more thing to find.
• Enlarging is off by default. Scaling a 400px image up to 2000px makes a soft file that is
  larger on disk and better in no way.
• Orientation is resolved once, at decode, and the output is tagged upright. Sizing against
  the stored rather than the displayed dimensions caps portrait photos on the wrong edge; the
  fix is pinned by two tests against real iPhone HEICs.
• Transparency is flattened onto white for JPEG, which has no alpha channel. CoreGraphics
  leaves an untouched buffer at zero, so the default is black and a dropped-out logo comes back
  unreadable.
• Camera metadata is carried across, minus the tags describing the old pixels — an EXIF
  width of 6000 on a 2000px file is worse than an absent one. GPS comes across too; that is
  noted in the README rather than decided on anyone's behalf.
• "Same as original" falls back to JPEG for formats macOS reads but cannot write, and says
  so in the status line. Finding the wrong extension in Finder a week later is worse.

Fixed during the build

• Letters could be typed into the size fields. SwiftUI's TextField(value:format:) leaves
  the binding at its old value when the parse fails, so the field showed text that did not match
  the number behind it — and a width of 1 got committed without anyone typing it. The fields
  now hold text and derive the number, filtering as you type and settling on blur.
• The window accepted a drag of any file. onDrop(of: [.fileURL]) matches the pasteboard's
  declared type, not the file, so a dragged movie lit the border up and then vanished on release
  having done nothing. Drags are now refused properly through AppKit, and anything dropped by
  name and skipped is reported.
• AppVersion's synthesised == contradicted its <, making "1.2" and "1.2.0" different
  releases.
• The width field came up focused and stayed focused, so anything typed after adding images
  went into it and overwrote the number already there. Nothing takes keyboard focus at rest now;
  the fields are for when you click them.
• A cancelled "Choose a folder…" could persist across launches, bringing the app up with
  Process disabled for a reason set in a previous session. It falls back to writing beside the
  originals, as it does if a chosen folder has since been deleted or unmounted.
• The grid hung the window when a tile was dragged. The frame reporter sat inside the offset
  it was measuring, so moving a tile changed its measurement, which moved it again. There were
  no crash reports because it was never a crash — just a beachball.
• The first background wash was three saturated blobs and looked like a bruise.

Versioning

./VERSION is the single source of truth. Scripts/version.sh syncs Info.plist from it and
refuses to move backwards; swift test fails if the two drift apart, if the version is not
semver, or if this file has no section for it. There is no CI, so the test is what actually
enforces it.