![]() ![]() This is because it then gives me a more capable way of identifying shortcuts than just by the name of the shortcut. As you might have guessed from the details above, I do not feel the need to document every single Shortcut, but through use, I have found I am documenting some of the simpler shortcuts as well as the more complex ones. Summaryīeing able to bidirectionally link to a note in Obsidian to create documentation for my shortcuts is very useful to me. This then allows Hook to do its association “magic”. Once in place, this will allow you to generate an edit shortcut link when you are editing a shortcut in Apple Shortcuts. "shortcuts://open-shortcut?name=" & encode_text (( the clipboard as text ), true, true ) & ")" `menu_click`, by Jacob Rus, September 2006 - Accepts a list of form: `) delay 0.2 tell application "System Events" keystroke "c" using command down delay 0.2 keystroke return delay 0.2 end tell return "(" & ¬ It should be added in the Get Address section as the script returns a Markdown link. ![]() The script is added via the script editor in Hook’s preferences. The script also makes use of some helpful scripted solutions from others, which have been included verbatim and include references back to their creators and websites. It utilises the system clipboard to grab the name of the shortcut and build the edit URL from that - so it is doubly important to ensure that your shortcuts are uniquely named. While I have a pro subscription, and Shortcuts does support using URLs for open a shortcut for editing, Shortcuts is somewhat ironically not particularly scriptable.Īfter applying a little thought to the situation, I was able to put together an AppleScript that interacts with the Shortcuts application’s user interface, which then enabled me to allow an address to be generated by Hook for a particular shortcut. Pro subscribers of Hook can create their own integration scripts that allow Hook to work with any app capable of supporting hyperlinking to a specific resource. To do this it relies on access to unique identifiers, URL schemes and a way to programmatically reference these through Hook’s integration scripts. Hook allows me to create bidirectional links between resources to associate them. As a result, like my other automations, I document some of my Apple Shortcuts automations in Obsidian, and my preference is to use the Hook application to support that. Regardless, the complexity of such Shortcuts solutions inevitably leads to a need to document in order to fully support its use and maintenance. ![]() Personally I break my shortcuts down into smaller more reusable shortcuts - a typical developer approach but this does mean that these multi-shortcut solutions are not as easily shared with others. Some people build shortcuts with hundreds of actions. While statistically most shortcuts are probably less than a half-dozen actions, there are inevitably more complex ones. Shortcuts is a natural successor to Automator - or in effect, what Automator could easily have become if the investment had been there at the time. ShortcutsĪpple’s Shortcuts application came to the Mac in 2021 and provided Mac users with the latest functionality in native Apple automation. In this post I will aim to explain how I am using this set up to help me access documentation for my Apple Shortcuts automations. Automation Documentation: Hooking Apple Shortcuts Įarlier this week I wrote about how I was using Hook and Obsidian to support my documentation of automations. ![]()
0 Comments
Leave a Reply. |