Readers of this blog know how important DEVONthink is to my workflow. I use it as a central repository on my Mac for almost every piece of information in my professional and personal life, including as a place to store personal and business records, deposition data, jury verdict reports, legal research, trial notebooks, and more. I’ve been using DEVONthink 2 for over 7 years, during which time the program has seen frequent updates and improvements. Now, though, DEVONtechnologies has released an entirely new version of DEVONthink for the Mac.
Category: Mac (page 1 of 26)
Your Caps Lock key might be underused on your Mac. If you’re a big automation geek, why not use it for something else, in addition to its built-in functionality? Karabiner Elements is a Mac tool that lets you customize the keyboard on your Mac, including the Caps Lock key. In this post, I’ll talk about how I’ve set up my Caps Lock key to be used as an extra modifier key (similar to the Command, Control, Option, and Shift keys), while at the same time preserving its normal functionality.
In addition to attending great sessions and meeting interesting people, I presented two sessions at the ABA TECHSHOW in Chicago last week. One of them, Mac Mastery: Top Mac Workflows Used By Real Attorney, featured a few automation workflows and other processes I use in my practice. I shared a link to a page during the presentation, and indicated I would later publish downloads of the various workflows to the page. That page is now populated with the downloads and other information:
You can never own too many text editors. Okay, I can never own too many text editors. I recently splurged on BBEdit, the venerable HTML and text editor for the Mac. There’s something pleasurable about tweaking BBEdit to use it as a blogging tool. One such tool I hacked together is an AppleScript to send a post from BBEdit to MarsEdit for final publishing. Here’s how you do it.
Paste the following text into the Script Editor app on your Mac (warning: I’m no coder, and did this through trial and error based on other scripts, so this script probably contains some completely unnecessary code):
on run
tell application "BBEdit" to set theFile to file of document 1
set appleScriptPath to theFile as text
set currentURL to POSIX path of appleScriptPath
set currentURL to ("file://" & currentURL)
tell application "MarsEdit"
activate
make new document
tell document 1
set body to theFile
end tell
activate
end tell
end run
Compile then save the AppleScript. For the final step, you need to move this AppleScript to the BBEdit scripts folder. Get there by clicking on the Scripts icon near the far right of the BBEdit menu, and choosing “Open Scripts Folder.”
Once the AppleScript is in place, it will appear at the bottom of the dropdown when you click on the Scripts icon. Selecting it will take the text in BBEdit, and open it in a new MarsEdit document. I wrote the initial draft of this post in BBEdit, before using the AppleScript to send it to MarsEdit for final edits, adding of the image, assigning tags and categories, and sending off to WordPress.
The point that some iPad die‐hard fans seem to miss is that it’s not a matter of people not wanting to adapt to an iOS‐based workflow; it’s not a matter of people lacking mental agility to ditch their computers and switch to iPads for work. It’s that their work imposes different solutions, in the form of dedicated software, company‐issued computers, multitasking requirements (e.g. ability to monitor more than three applications simultaneously on a bigger screen), etc.
Although the “why I can or can’t use the iPad as my only computer” topic has been covered ad nauseam, and although Riccardo’s post focused on the portability and lightness aspect as a draw for iOS, the above quote is what struck me.
While I love the change of pace of working on my iPad when I can, it simply isn’t possibly when things are flying fast and furious at the office. And that has nothing to do with me not being familiar enough with iOS or iOS automation to bend the iPad to my will so I can react quickly. Instead, it has everything to do with the design decisions of the iPad concerning windowing and multi-tasking, as well as the limits of automation on iOS1.
I can’t instantly jump between apps on the iPad as quickly as I can on the Mac, or keep more than a couple windows on screen at once (three, if you count slide over). iOS automation isn’t to where it is on macOS yet, either. For example, with Keyboard Maestro on macOS, I can apply a brute force filter to entries in our firm’s case management system, using Keyboard Maestro’s ability to click on specified images. With the iPad, I have to do this clicking manually. The iPad method takes several seconds longer, and, for me, those seconds count.
For my type of work, the iPad is good when I know what I need to get done, and can control my work environment. When I have to be reactive, though, I need a system with windowed apps, and more advanced multi-tasking and automation (i.e., macOS).
I’m glad Ricardo framed this as “some” iPad users missing the point. I think most of the people in my online circle seem to understand that what works for them doesn’t work for everyone. I certainly understand that my way of doing things is specific to me, and that the iPad is a much better platform for some of you.
(But don’t get me started on the ergonomic and future health issues of working solely on an iPad or laptop.)
This post isn’t meant as a suggestion that there’s something inherently wrong with those design decisions, or that Apple should change them – just that they hold me back in some situations.↩