Apple has updated a documentation page detailing the company’s next steps to prevent last week’s Gatekeeper bug from happening again, as Rene Ritchie spotted. The company plans to implement the fixes over the next year.
Apple had a difficult launch day last week. The company released macOS Big Sur, a major update for macOS. Apple then suffered from server-side issues.
Third-party apps failed to launch as your Mac couldn't check the developer certificate of the app. That feature, called Gatekeeper, makes sure that you didn't download a malware app that disguises itself as a legit app. If the certificate doesn’t match, macOS prevents the app launch.
There’s yet another update to Text Case, and it brings with it three new formats, theme syncing, and an action extension for the macOS version!
Smart Quotes – This changes any straight single of double quotation marks, into their curly equivalents, all based on your localisation.
Small Caps – ᴛᴜʀɴ ʏᴏᴜʀ ᴛᴇxᴛ ɪɴᴛᴏ sᴏᴍᴇᴛʜɪɴɢ ʟɪᴋᴇ ᴛʜɪs!
Upside Down – Just another fun one, this attempts to flip the characters upside down.
These new formats are available on all versions of Text Case, iOS, iPadOS, and macOS.
Automatic Theme Syncing
Text Case has support for themes, but previously you would have to manually switch between them. With this version, you can select “Automatic” to have the Text Case theme sync with the light/dark mode of your system. This works on both iOS, iPadOS, and macOS!
Format Text Action Extension for macOS
On the iOS/iPadOS version of Text Case, there’s an Action Extension that lets you select text anywhere, and then get direct access to the different formats in Text Case. This is now coming to the macOS version, with essentially the same behaviour.
Now you can select a portion of text anywhere in macOS, right-click, and under “Share”, there should be a “Convert Text” action. (If it doesn’t appear, you will have to go to System Preferences, Extensions, Actions, etc enable it.)
That will bring up the Text Case UI, and selecting a format will result in the formatted text being copied to your clipboard!
I’ve been slowly working on this for quite a few months now, but I think it’s finally time to release Text Case for Mac.
With it comes all 32 formats that are currently supported in the iOS app, and the same customisation options (except custom app icons).
To recap all of those:
Title Case (AP, APA, CMOS, MLA)
Markdown Code Block
Markdown Ordered/Unordered List
Markdown to HTML
In fact the macOS version is 2.4.4, and the iOS version is sitting at just 2.4.3. The only differences being some improvements to the Emoji format, where some localisations could cause the format to not work at all (it now defaults to English if it doesn’t support the language). And also some macOS specific changes, which are mainly to remove parts of the app that won’t work such as Siri Shortcuts support, and also fine tuning the macOS experience.
There are things that I’m already planning on adding the Mac version, such as an Extension so you can format text from outside the app, similar to how the Action Extension works in IOS, and also other automation support such as URL schemes. However, I feel that it’s much more beneficial for people to have Text Case for Mac now, rather than waiting even longer to get it into peoples hands. Because just like the iOS app, I really like to adapt the app to users feedback, and I already have a few extra formats (such as small caps) that I plan on adding soon. I also want to see what I can do with the Touch Bar!
Quick Look, the infinitely valuable tool on the Mac that lets you near-enough instantly preview a file. It’s really impressive the number of file formats it supports, but there are always going to be a few things it doesn’t. And that’s where plugins come into it.
One great one that I discovered via twitter today is QuickLookJSON. I’m sure you’ve already guessed what it does. But anyway, I may as well show you as well.
It not only displays JSON files though, it indents them properly, applies a colour scheme, and also lets you expand and collapse any of the data. That last one alone makes it super easy to navigate through a big JSON file.
I’m really glad to be announcing a project that started at the end of last year. 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.
This is something really only he could do. I’ve had a look through some of them, and it’s fun to see how the OS has evolved, and to see the iterations between big changes.
I’ve just upgraded my Mac to the latest Mojave beta, and I’ve discovered a new wallpaper!
In a previous update the Desktop Pictures folder was split into two sections – Dynamic Desktop and Desktop Pictures. The first section containing the photo of the Mojave desert, which contained a dynamic, and two still (night and day) versions.
This new one is called “Solar gradients” and comes in just a dynamic format. Of course it’s a rather simple wallpaper, and the majority of the time it’s a two-colour gradient, but it will show you the sun rising, the sky getting brighter, followed by the sun fading away, and a darker blue and black combination for the night sky.
A quick tip – If you want to preview a dynamic desktop, when you navigate to the Desktop & Screen Saver pane in System Preferences, just select the wallpaper, and the preview image will cycle through the different segments.
Stationery Pad is a handy way to nix a step in your workflow if you regularly use document templates on your Mac. The long-standing Finder feature essentially tells a file’s parent application to open a copy of it by default, ensuring that the original file remains unedited.
Stationery Pad doesn’t get much attention these days, but it’s a neat alternative to repeatedly editing templates and using the “Save As…” command, which can lead to overwriting the original file if you’re not too careful.
I had no idea this existed. I will most certainly be making use of it in the future.
Say you write an iOS app, and now you want to write the Mac version.
Assuming there’s a data model, maybe a database, some networking code, that kind of thing, then you can use that exact same code in your Mac app, quite likely without any changes whatsoever.
I agree with Brent here. I’ve never really understood the argument that AppKit is that difficult to understand, so that’s why people don’t port native apps over. Surely the underlying logic of the app is the hard part, and linking the functionality to the interface is the easier part?
I would say I’m more of an iOS developer, simply because I’ve spent more time on it. But I’ve also made a few Mac applications. Sure, a resizing window is a bit more complex than a relatively fixed screen size, and some the interface elements are names slightly differently.
It’s just different, for both sets of people. But not as difficult as it may seem.