Working with extended attributes in Swift. They’re straightforward using shell commands, but that is not the best way ahead.
Xcode
This tool for Sierra now inspects and displays extended attributes, and will write a quarantine xattr to force a full Gatekeeper check on an app, as if downloaded.
If you want someone else to be able to run your script app, you’ll need to sign it and get it past Gatekeeper’s checks. Here are more details about the role of xattrs in those, and how to run a full check without downloading your app.
How much more difficult is it to write your own code to handle user preferences, rather than letting UserDefaults handle them?
Which String.contains() variant should you use, and how can you give access to regex searching? More answers coded in Swift 3.1.
Creating a drop-down sheet to let the user change preference settings is a bit intricate, but straightforward.
In some respects at least as good as any other Swift playground product, and its AppleScript support has improved considerably. But in other respects still falls short. In a class of one.
The code scrapbook is finished, and has now produced its first set of articles. Five articles in around ten minutes seems pretty impressive to me.
Calling shell commands, including with privileges, NSBackgroundActivity, XPC Activity, and writing shell commands in Swift.
Dates with (NS)Date and DateFormatter, writing messages to Sierra’s unified log, and working with old Objective-C interfaces.
