With Kaleidoscope 3.8, we’re bringing you a new workflow to compare Pages documents, powered by Shortcuts and AppleScript. As the initial setup is a bit of a challenge, we’re showing you how to do it, step by step.
Developers make up the largest segment of Kaleidoscope customers. Many of you use the Git version control system to manage your source code, regardless of the programming language you may be using. The Kaleidoscope team also uses Git, and today we want to tell you about an app that most of us use on a daily basis.
There’s an obvious synergy between Tower and Kaleidoscope: Tower is a great front end to Git’s change management and Kaleidoscope is a tool for dealing with changes. Here are a few scenarios, beyond comparing two files, that may not be obvious and can help you optimize your workflow.
Over the last few months, we’ve received several feature requests for the ability to compare the contents of archives like .zip or .jar. Indeed, an archive is really a folder full of files, a folder that happens to be compressed into a single file. So we should be able to compare archives using Kaleidoscope.
Today we are happy to announce that, as of Kaleidoscope 3.5, comparing archives is possible, via a brand new action for Shortcuts.
VSCode is a powerful IDE that can be used with all the world’s programming languages through a vast ecosystem of extensions.
And now there is one more. The new Kaleidoscope extension for VSCode allows you to compare entire files, compare a selection of text, show git difftool results and run git mergetool.
The extension provides these functionalities through a comprehensive set of menu choices and toolbar buttons.
The extension allows you to send HTML or CSS to Kaleidoscope, enabling you to compare the changes you are making, while you iterate on your latest web page or web app.
Most developers for Apple platforms deal with tests in some way or another. XCTest is probably the most popular framework because it’s built directly into Xcode and can be integrated with build processes and automation.
However, one problem with those tests is that more complex failures are not easy to interpret. And if things aren’t easy (and fun) to use, developers will have a resistance to using them. Wouldn’t it be nice if Kaleidoscope could show XCTest failures in a useful format?
The other day we found a helpful command line tool option, only to discover later that the option was only available in macOS Monterey. Since we also need to target Big Sur, this would not be an option for us. So we created something to help us overcome similar issues in the future: a way to compare man pages between macOS system versions. And that’s what we want to share with you today.
As a long-time Mac user, I’ve seen lots of productivity tools come and go, and I’ve used a fair amount of them through the years. Who still remembers Quicksilver (β)? It was pretty awesome at the time… Other notable mentions for me personally are Butler by my dear pal Peter Maurer and LaunchBar. There are also still new kids on the block, like RayCast.
However, the one I keep coming back to and that is running 24/7 on my Mac is Alfred. I particularly like its combination of easy discoverability of the more mainstream features and the sheer power it hides by default, but offers when you need it.Read More »Integrating Alfred and Kaleidoscope
It was October 2018 when Christopher had the idea to integrate Kaleidoscope with lldb, the Xcode Debugger. Back then, he tweeted a gist that showed how to get this to work for his needs.
Many moons later, in February 2021, that feature is finally available to every Kaleidoscope user, configurable with the click of a single button.