A Whirlwind First Week
Last Tuesday I posted a video introducing Tug and “officially declared” the app a beta (as much as this matters for open-source projects… the code was right there all the time 😉). I’ve been heads-down ever since. Here’s a catch-up on all the work and progress.
tl;dr: four releases in five days, the first bug reports from people out in the world, the first code contribution from someone other than me, four more videos, and a new short address for the project. It’s been a whirlwind! 💨
Four releases
Tug is now at version 0.9.3.
0.9.0, last Monday evening, was the first beta, and the jump from 0.8.x to 0.9.x marks that. It was a broad release. A session that finished its turn while I was looking at another card now shows as Done, instead of looking like it’s still running. Find and replace works everywhere I edit text. There’s a new Text menu, with transforms like case changes and comment toggling.
0.9.1 came the next day. I called it the inevitable oops release in the release notes, and that’s what it was: keyboard and focus fixes for things I broke or missed on the way to 0.9.0.
0.9.2, a day after that, added a Getting Started help card that opens the first time you set up a session, and included a theming audit that fixed a number of wrong colors.
0.9.3, on Saturday, is the big one. Share Turns lets me hand part of a session’s conversation to someone else as a PDF, an image, or Markdown. Add Project Directory lets a session reach into a second folder. Typing @ in the prompt now offers sessions and commits alongside files. Switching workspaces is immediate.
More than anything, though, 0.9.3 is the release that fixes bugs reported by people trying Tug for the first time. The full notes for every version are on the releases page, and the app updates itself, so if you already have Tug, you already have all this.
Thank you
For nine months, I was the only person using and hacking on Tug. I made it for myself, as I’ve said here before, though I had my hopes that other people might like to try it (and would like it if they did!). This week, people did, and some of them took the time to tell me what went wrong and send ideas to improve the app. Open source FTW!
So, some thanks.
Justin Garcia (@littlebobert) sent a crash report and a few questions on the first day of the beta. The crash was in a command I had retired and forgotten to remove. He also noticed that /add-dir would autocomplete but not run, and he asked for faster tooltips. All three are fixed in 0.9.3.
Justin also asked for Tug to bounce its dock icon when a session finishes or needs input, and he offered to do the work himself. The same day, he sent a pull request, and I merged it on Sunday. It’s the first code in Tug written by someone other than me. It adds a Session Notifications group to the settings.
Chris Messina (@chrismessina) found that installing Tug stopped Pixelmator Pro from opening its own documents. Tug had claimed the .pxd file extension for Cython source files, and Pixelmator Pro uses the same extension. Chris didn’t just report it. He diagnosed it and suggested the fix.
Jérôme Danthinne (@jdanthinne) reported that keyboard shortcuts landed on the wrong keys on his AZERTY keyboard. On a non-QWERTY layout, Tug answered to the key in the US position, so Command-A could quit the app. Ouch. Shortcuts now follow the keyboard layout.
Gene (@SemitoneGene) spotted that Finder’s window controls covered the text on the installer’s background image.
Tito Ciuro suggested that Copy in a Session card should give plain text by default, that renaming a session should be possible right in the card’s masthead, and that Command-click should open a file reference exactly as a plain click does. All three are in 0.9.3.
And I should go back a little further, to Marc Verstaen (@verstaen), who filed the first issue from outside in October, before the beta. He had built the app from a fork, and it crashed at launch. I reproduced his crash in a virtual machine and had a fix out the next day. This made Marc’s the actual, very first outside bug report.
If you’ve tried Tug and hit a problem, please tell me about it. I’m trying to listen and respond as soon as I can… which is part of the reason this post fell behind the work and progress on Tug!
More videos
I’ve been posting videos on my YouTube channel too.
After the intro, I made Getting Started with Tug, a quick tutorial. It walks through the prompt, monitor, review, commit workflow while I build a small calculator program in C. (Yes, in C. Heh.)
I’ve also started making shorts, each about one small detail of the app. Here are the first three.
The shorts format works for me. One detail, one quick video. There are a lot of details in Tug that I’d like to show this way. I also spent a bunch of time with the AI to develop a workflow and pipeline to make these shorts.
I made a new app from scratch to generate the as-I-speak captions. Once I polish up that app a little more, I’ll release it as open source.
A shorter address
One more thing. Tug now has a short address: tug.now. It takes you straight to the Tug home page. I got it so I’d have something easy to put on screen in videos, and easy to say out loud.
What’s next
More of the same, I hope. More releases, more videos, and more feedback from people using the app.
If you’d like to try Tug, download it and let me know how it goes! 🚀