Omni Automation Video

002: Installing and Managing Plug-Ins
A short overview of how to install and manage Omni Automation plug-ins.

Related Links: (Podcasts)

Transcription:

(:00) (TOP) Welcome to Omni Automation Podcast, number two: “Installing and Managing Plug-Ins”

(:08) (TOP) Plug-Ins are individual files and bundles, that focus and extend the abilities of Omni applications.

(:14) (TOP) These plug-ins, composed in JavaScript, are saved using a specific naming convention.

(:23) (TOP) The file extension for a plug-in begins with the name of the plug-in’s Omni application, followed by the letters: “j” and “s”, and is preceded with a period, and the name of the plug-in file or bundle.

(:37) (TOP) Plug-Ins that target more than one Omni application, use a file extension of: omni j s, which is also preceded with a period and the file name of the plug-in.

(:49) (TOP) Omni Automation Plug-ins can be installed using any of three methods:

(:54) (TOP) By activating an “Install Link” embedded in a webpage....

(:57) (TOP) By downloading and opening a plug-in file or bundle.

(1:00) (TOP) Or by moving the plug-in into one of the default Omni plug-ins folders, or a folder “designated” by the user to serve as an Omni plug-in directory.

(1:09) (TOP) With “Install Links,” simply activating a link in a webpage, will automatically trigger the targeted application’s plug-in onboarding process.

(1:21) (TOP) This plug-in “Installation Dialog,” is used by all Omni applications, and appears when triggered by an “Install Link,” or by opening an Omni Automation plug-in, that has been downloaded to the Finder or Files app.

(1:33) (TOP) This dialog displays information about the plug-in, including its host app, its file name, author, and description of what the plug-in does when activated.

(1:43) (TOP) In addition, it displays a warning that you should only install plug-ins that come from trusted sources.

(1:51) (TOP) The dialog also contains a control for determining the folder in which the plug-in file is to be stored, and controls for either stopping or proceeding with the plug-ins installation.

(2:03) (TOP) The “Plug-In Location Menu” displays a list of all default and user-chosen plug-in storage folders; including the host app’s local support folder, and the host app’s corresponding iCloud support folder.

(2:17) (TOP) Plug-Ins stored in the app’s iCloud Drive folder, will be automatically available on all Apple devices signed into the user’s iCloud account.

(2:30) (TOP) Once installed, the plug-in’s menu title will appear on the Omni application’s Automation Menu.

(2:39) (TOP) Managing Installed Plug-Ins

(2:43) (TOP) To manage installed plug-ins, select the “Configure…” menu option on the Automation Menu.

(2:51) (TOP) The “Automation Configuration” dialog, will be displayed.

(2:56) (TOP) To access the “Automation Configuration” dialog, on non-Mac devices, select the “Options” menu item; then the “Settings” menu item; then the “Automation” option; and finally the “Manage Plug-Ins” option.

(3:13) (TOP) You can also select the “Manage Plug-Ins” option, from the Automation Menu.

(3:25) (TOP) The Automation Configuration dialog, displays a list of default and user-approved plug-in storage folders, as well as showing which plug-ins have been installed into the directories. There are also controls for linking to, and un-linking from user-chosen directories, for storing installed plug-ins.

(3:44) (TOP) On macOS, double-clicking a listed storage folder, will reveal and open it on the Desktop.

(3:53) (TOP) And selecting a listed plug-in, will enable the control, for revealing the plug-in file in the Finder.

(4:03) (TOP) Selecting the “Information” icon, for the installed plug-in, summons the “Plug-In Information Sheet.”

(4:11) (TOP) This sheet is divided into two sections: metadata regarding the plug-in file; and metadata for each of the plug-in’s actions.

(4:20) (TOP) The metadata for the plug-in includes: the plug-in filename; version; author, and description.

(4:28) (TOP) The metadata for each action includes: the action’s icon; the text of its Automation Menu item; and the action’s description.

(4:38) (TOP) In addition, there is a control for assigning a “keyboard shortcut,” for triggering the execution of the plug-in action.

(4:45) (TOP) To set a “keyboard shortcut,” select the control, and type the key combination to be assigned.

(4:52) (TOP) To approve the changes, select the “Done” button, to dismiss the “Plug-In Information Sheet.”

(5:01) (TOP) For extensive detailed information about Omni Automation plug-ins, please visit: omni-automation.com/plugins. Thank you!