The Shape of Everything
A website mostly about Mac stuff, written by Gus Mueller
» Acorn
» Twitter
» Maybe Pizza?
» Code
» Archive
March 16, 2017

Up here at the FM world headquarters, I've recently pushed the buttons and typed the commands to make Acorn 5.6.4 roll out to all my favorite people.

It's purely a bug fix release, but it includes a fix for a 10.12 issue that I've spent way too long tracking down. So if you're on 10.12 Sierra, and you've seen the occasional case where a black box would suddenly appear somewhere on your canvas, this release is for you.

So start your update engines and grab it today.

And a small request: if love Acorn and you've purchased it via the App Store, why not leave it a nice review or give it a handful of stars? When we push out new releases, it resets the previous reviews and ratings in the store which is a huge bummer for us (and it also creates a disincentive for releasing bugfix builds! But that's a story for another time). We love getting reviews and ratings though, it's like fuel for future releases.

February 17, 2017

This video is the best thing I've seen in the climbing community for a long while.

Diversity has always been huge problem in the climbing world. I'm glad Brothers of Climbing is helping to fix it.

February 10, 2017

Piezo’s Life Outside The App Store

Paul Kafasis talks about what sales and revenue for Rogue Amoeba's app Piezo looks both in the App Store, and out of it.

January 18, 2017

"Today, you are an Astronaut. You are floating in inner space 100 miles above the surface of Earth. You peer through your window and this is what you see. You are people watching. These are fleeting moments.

"These videos come from YouTube. They were uploaded in the last week and have titles like DSC 1234 and IMG 4321. They have almost zero previous views. They are unnamed, unedited, and unseen by anyone but YOU."

This video stream(s) are mesmerizing. At first, I thought they must have been curated somehow. But then I took a look at the number of views of them, and the count was usually under ten. I think they really are random. It's amazing.

Motion Graphics For The Web is impressive.

I was jealous of Instagram's wide gamut canary image, so I made my own with FM's logo.

If you're on a wide gamut display, you'll see our logo. If you're not… well, you won't. Unless the app you're in handles color profile badly.

January 16, 2017

I spent more time this morning than I care to admit trying to suss out a code signing issue for Acorn when launching for the first time on 10.10. Here's my little story, and maybe you'll figure things out faster than I did.

Direct builds of Acorn were failing to pass through Gatekeeper on 10.10, but the exact same build worked fine on 10.12.

Running /usr/bin/codesign --verify was telling me something was wrong, but not what. However if I resigned my "bad" copy of Acorn using codesign on 10.10, then it passed through Gatekeeper without a hitch.

I was confused. So I went back through previous builds of Acorn (I keep copies of every in-progress beta build) to find where exactly the problem started showing up, and it occurred when I upgraded my build script from Xcode 7.3.1 to 8.2. I still didn't understand why codesign would be failing though, since that is run via a script against the final build, outside of Xcode's usual build process.

I pinged some friends for ideas and Daniel Jalkut suggested I try codesign --verify, but this time with the --deep option included. The extra argument pointed out the exact bundle in Acorn which was causing things to fail on 10.10. It was an Automator bundle.

I opened up that Automator project in Xcode and noticed right away that its deployment target was empty, which means it'll get whatever that version of Xcode thinks is right. In Xcode 8.2 that probably means 10.12, not 10.10.


There are a handful of Automator projects for Acorn, and I'm lazy and didn't want to check them all. Instead I chose to add the option MACOSX_DEPLOYMENT_TARGET=10.10 to xcodebuild when compiling those projects, and all was good.

Here's what I think was going on.

When codesign on 10.12 was run against the Automator actions, it checked to see what the deployment target was and signed the bundles in a way that wasn't compatible with 10.10. However, if I explicitly set the deployment target to 10.10, then codesign (running on 10.12) would then sign the bundles in a different way which was compatible with 10.10.

I think. I could be wrong. Maybe I should be substituting 10.11 in there for for 10.12 or 10.10. But it's all working now.

Anyway, thanks Daniel. And future Gus should remember the --deep option. (P.S.: The full command Daniel gave me was:
codesign --verify --deep --strict --verbose=2

A neat concept design for a hypothetical Mac Pro 2.

The current one is dumb. It's too small and you can't expand it.

So I've got a micro blog now. It's the new hotness. This is an entry from it as well, and here's the feed:

Science Bulletin: Study finds association between eating hot peppers and decreased mortality.

As a person who frequently eats spicy food, I welcome this news.