Skip to content

Releases: mlemos/parker

Parker 1.1.0

Choose a tag to compare

@mlemos mlemos released this 09 Sep 05:25

To-dos get a priority, and a bolder set of checkboxes.

Priority. Add one to three bangs right after the tag — /TODO!, /TODO!!, /TODO!!! — and the empty box's border takes the colour of the level: green for a plain to-do, then yellow, orange and red. The bangs stay behind the box, and ⌘⏎ or a click keeps them when the state changes. /TODO !! with a space is just a to-do whose text starts with !!. Filled boxes are unchanged: their fill already says the state.

Checkboxes. Play, pause and the hourglass are now solid; check, x, asterisk and minus are heavier to match. The play triangle also sits where Lucide draws it — it was 3% too large and a touch to the right.

Requires macOS 12+ on Apple Silicon. Signed with an Apple Developer ID and notarized.

Parker 1.0.2

Choose a tag to compare

@mlemos mlemos released this 08 Sep 21:07

Parker's bundle identifier is now dev.getparker.parker, matching the product's domain — and the identifier the upcoming iPhone companion will share. Nothing about your notes, git setup or settings moves.

Two one-time effects on first launch after updating:

  • macOS asks again for access to your Documents folder. The system ties that permission to the identifier, so it is a fresh question. Click Allow once and it stays.
  • Three editor toggles return to their defaults — line numbers off, line wrap on, ligatures off — because the old values lived in the web view's storage, which the identifier change leaves behind. They now live in Parker's own settings.json, alongside zoom and git, so this cannot happen again.

Requires macOS 12+ on Apple Silicon. Signed with an Apple Developer ID and notarized.

Parker 1.0.1

Choose a tag to compare

@mlemos mlemos released this 08 Sep 07:05

A small release that fixes what got in the way when moving tabs around.

Fixes

  • 🧲 Dropping a tab onto a pane's body now moves it there — before, only the tab strip accepted the drop.
  • 📐 Pane dividers sit flush against the panes, with no gap on either side.

Better drag feedback

  • A bar shows exactly where a dragged tab will land — including when it comes from another pane, and past the last tab.
  • A pane you can drop on shows a ring instead of tinting green.

Requirements

  • macOS 12+ on Apple Silicon (arm64). Signed with an Apple Developer ID and notarized by Apple.

Download: Parker_1.0.1_aarch64.dmg

Parker 1.0.0

Choose a tag to compare

@mlemos mlemos released this 08 Sep 05:11

Parker's first signed & notarized release. Download it, open the disk image, and drag Parker to Applications — it just runs, with no Gatekeeper "damaged" warning and no Terminal workaround.

Highlights

  • 🔏 Signed with an Apple Developer ID and notarized by Apple (both the app and the disk image)
  • 🎨 Eight themes, plus a to-do palette the theme owns
  • 🛟 More reliable saves — a note no longer conflicts with Parker's own save, or with itself

Requirements

  • macOS 12+ on Apple Silicon (arm64)

Download: Parker_1.0.0_aarch64.dmg

Parker 0.4.6

Choose a tag to compare

@mlemos mlemos released this 26 Aug 06:43

A fix for something that only happened on a brand-new note.

Creating a note no longer conflicts with itself

Press ⌘N, type a character or two, and Parker would put up “Changed on disk while you were editing” — offering to reconcile the new note against a version of itself that nobody had written.

Nothing had changed on disk. ⌘N creates the file empty, the folder watcher takes about 150ms to report that creation, and if you started typing inside that window Parker compared the file (correctly empty) against the buffer (one character) and concluded that someone else had been in there.

The mistake was in what the comparison asked. Parker checked the file against your buffer, which conflates two different questions — do I have unsaved edits? and did the file change underneath me? The first is the ordinary state of typing. A buffer now remembers what Parker last saw in the file, and only a file that differs from that counts as an external change.

If you hit this, nothing was lost: Parker refuses to autosave a note with an open conflict, so the file stayed as it was and your text stayed in the buffer. Choosing either button resolved it.

A save that raced a keystroke said it had saved it

Writing a note is awaited, and a character typed during that await was not in the bytes that reached disk — but the note was marked clean anyway, so autosave had no reason to come back for it. The last character of a fast sentence could sit unsaved until the next edit. The save now compares what it actually wrote.

Note on first launch

The app is ad-hoc signed, so macOS shows a Gatekeeper warning the first time you open it, and asks again for access to your Documents folder after each update.

Parker 0.4.5

Choose a tag to compare

@mlemos mlemos released this 26 Aug 06:23

Four new themes

Parker had four themes, all of them monochrome chrome over vivid syntax. It now has eight, and the four new ones are somewhere else entirely:

  • Playa — noon, white dust, hard sun, nothing in shade. The only light theme here that isn't paper: the ground has a colour of its own.
  • Playa at Night — the same place after dark, when everything visible is lit from within.
  • Matrix — phosphor green on black. One hue and a brightness ladder, which is what a P1 tube actually gave you.
  • Blueprint — cyanotype: pale technical linework on deep drawing-office blue, where white is the ink rather than the paper.

⌘⇧T cycles through them. The palette button had promised that shortcut for a while and nothing was listening; now it is. Double-click the button to go back to the default.

To-do colours now belong to the theme

The eight to-do states used to be eight fixed colours. That works only while every theme has the same kind of ground — and Matrix does not. Its body text is green, so the old DONE was green on green: the state that matters most was the one you couldn't read.

Each theme now names its own. On the playa, DONE is creosote and ATTN is the sun; on the phosphor tube, DONE is the tube at full brightness and ATTN borrows the amber of the other tube these terminals came in. The relationships hold everywhere — arrival, its approach, two kinds of stall, the two failures — only the colours change.

On the light themes the marks stepped down a rung, because the old ones washed out on white.

Three shortcuts that were lying

  • Copy line is ⇧⌥↑ / ⇧⌥↓. The help window said ⌘⌥↑ / ⌘⌥↓, which adds a cursor above or below — a real shortcut that was hiding behind the wrong label.
  • The empty pane offered ⌘T for a new note. New note is ⌘N; nothing was listening to ⌘T.
  • The default summon shortcut is ⌃⌥P. Some of the docs still claimed ⌥Space.

And two that worked but were never written down: ⌘⌥G goes to a line, Esc backs out to a single cursor and closes the find bar.

Also

The site grew a features page — getparker.dev/features — with real screenshots of all of this.

Note on first launch

The app is ad-hoc signed, so macOS shows a Gatekeeper warning the first time you open it, and asks again for access to your Documents folder after each update.

Parker 0.4.4

Choose a tag to compare

@mlemos mlemos released this 25 Aug 18:19

When a note changes underneath you

Parker reloads an open note when the file changes on disk — a git pull, another machine, another editor. Until now it did that silently, and if you had unsaved edits it quietly kept yours and let autosave write over the other version.

Now the lines a reload rewrote are marked in amber — line, number and gutter — and they stay until you type in that note. Not a flash: a mark you can still read when you come back from lunch. A chip in the status bar counts the notes waiting to be read.

When the file changed while you were editing, a bar asks instead of deciding: Use disk version or Keep mine. Autosave holds off on that note until you answer.

The tab dot now says what state a note is in

One dot, one colour: dimmed green when saved, cyan for your unsaved typing, amber for text that arrived from outside, purple for a conflict, red when a read or write failed — a failure that used to reach only the console.

Selection

Line numbers brighten along with a multi-line selection, and the selection itself now hugs the text instead of filling the line.

Note on first launch

The app is ad-hoc signed, so macOS shows a Gatekeeper warning the first time you open it, and asks again for access to your Documents folder after each update.

Parker 0.4.3

Choose a tag to compare

@mlemos mlemos released this 24 Aug 05:45

Collapsible sections

Fold a heading and its whole section goes with it, down to the next heading of the same or higher level. Fenced code, quotes and tables collapse too, and any line folds whatever is indented beneath it — which is what makes nested to-dos and lists fold.

A chevron sits in the gutter with the line numbers: visible on hover while a fold is open, and always visible once it is closed, because a fold that hides itself is a trap. The folded line's number takes the accent colour, and a badge in the text counts the hidden lines. ⌘⌥[ folds, ⌘⌥] unfolds, ⌃⌥[ and ⌃⌥] do everything at once.

The editor remembers

Each pane now keeps one editor with one state per tab. Switching tabs used to rebuild the editor from scratch, which meant losing the cursor, the scroll position and the undo history every time. All three survive now — and so do your folds.

Note on first launch

The app is ad-hoc signed, so macOS shows a Gatekeeper warning the first time you open it, and asks again for access to your Documents folder after each update.

Parker 0.4.2

Choose a tag to compare

@mlemos mlemos released this 22 Aug 06:19

Interface zoom

⌘= / ⌘- / ⌘0 now scale the whole window the way a browser or VS Code does, not just the editor's font. Tabs, gutter, editor and status bar move together, in the same frame. Rungs run from 50% to 300%, finer around 100%. The level is remembered and restored before the first paint.

Fixes

  • The line-number gutter no longer arrives a frame after the text when zooming.
  • Both chrome bars sat half a pixel off centre — their 1px border was eating into a fixed height. Corrected without changing either bar's height.

Note on first launch

The app is ad-hoc signed, so macOS shows a Gatekeeper warning the first time you open it, and asks again for access to your Documents folder after each update.

Parker 0.4.0

Choose a tag to compare

@mlemos mlemos released this 17 Aug 05:01

Parker 0.4.0

New to-do state: /DOING

The state between "open" and "finished" — a cyan checkbox with a solid dot, and the line's text in cyan to match. /WIP works as an alias.

It sits right after /TODO in both cycles, which is where work actually goes:

  • ⌘⏎ rotates the line: todo → doing → attention → done → fail → cancel → plain line.
  • ⌥-click cycles the open states: todo → doing → attention → fail → cancel.
  • A plain click still completes from any open state, and reopens a finished one.

The full set is now /TODO · /DOING · /ATTN · /DONE · /FAIL · /CANCEL, and the shortcuts window (⌘K) lists them.