Daniel Jalkut:
Until Paul mentioned his own problems, I glossed over these failures because I was satisfied that my production built versions, linked against the 10.13 SDK, were “working fine.” But Paul’s report got me thinking: was it possible there is some unspoken contract here, whereby linking against the 10.14 SDK opens up my app to additional privacy related requirements?
I tapped into Xcode’s Info.plist editor for FastScripts, added a new field, and typed “Privacy” on a hunch, because I’ve come to realize that Apple prefixes the plain-English description for most, if not all, of their “usage explanation” Info.plist fields with this word[…]
Aha, that first one looks promising. You can right-click on an Info.plist string in Xcode to “Show Raw Keys/Values”, and doing so reveals that the Info.plist key in question is “NSAppleEventsUsageDescription”. After adding the key to my app, I built and run again, and running the same script as above now yields the expected authorization pane[…]
I believe the WWDC session said that the other usage descriptions are required if you build with the macOS 10.14 SDK. NSAppleEventsUsageDescription was not added until Beta 7, though. It’s kind of odd that this key just has a single string value, since an app might want to send events to any number of different apps, for different reasons. Everything needs to go in that one string.
And it’s too bad there’s no corresponding usage description or prompt for Full Disk Access. Your app just gets a permissions error, and you have to explain to the user how to enable access in System Preferences.
Previously: Apple Event Sandboxing in macOS Mojave Lacks Essential APIs.
AppleScript Mac macOS 10.14 Mojave Privacy Programming Transparency Consent and Control (TCC) Xcode
Anil Dash (via Reddit, Hacker News):
But honestly, we’ve been resource-constrained as a small company to do justice to Manuscript, especially as Glitch has taken off and demanded our attention, and the market for software project management tools has gotten more competitive. So recently, we started looking at whether we could find a new home for Manuscript that would provide it with the investment and focus needed to not just support the current users and functionality of the platform, but to expand both.
I’m very interested to see how this turns out.
Update (2018-09-07): Andy Tryba:
Please join me as I unveil our vision and plans for Manuscript at our upcoming Virtual User Conference webinar on Wednesday, September 12th at 10am EDT.
Good thing it’s Eastern time.
Update (2018-09-13): Based on an e-mail I received, it looks like Manuscript is being renamed back to FogBugz and that DevFactory is using a different system for their customer support (rather than eating their own dog food, as Fog Creek did).
Acquisition Bug Tracking Business FogBugz Manuscript Web
Stephen Hackett (tweet 2, MacRumors):
I have worked my way through every major release of macOS since the Mac OS X Public Beta and catalogued them in an extensive collection of screenshots.
Currently, the library includes 1,502 images. That’s 1.6 GB worth of screenshots.
These images came from the OS, running on actual hardware; I didn’t use virtual machines at any point. I ran up to 10.2 on an original Power Mac G4, while a Mirror Drive Doors G4 took care of 10.3, 10.4 and 10.5. I used a 2010 Mac mini for Snow Leopard and Lion, then a couple different 15-inch Retina MacBook Pros to round out the rest.
Wow.
John Gruber:
I love the little things, like looking at how the Finder’s “Go to Folder” sheet has subtly changed over the years.
Previously: Mac and iOS Wallpaper Archive.
Design Finder History Mac Screenshots
Jason Pepas:
I often print pointer addresses as emoji. Handy when debugging issues related to UITableViewCell reuse etc.
It’s much easier to recognize 🎃 in a log than 0x00007fa2ec033200.
Here’s his Swift code.
Cocoa Debugging Emoji iOS iOS 11 Memory Management Open Source Programming Swift Programming Language
