EventScripts allows you to assign AppleScripts, shell scripts and Automator workflows to be run when certain events occur. Alternatively simply launch applications when events are detected.
EventScripts supports many events as below.
Mobile & Location Events
Application & Browser Events
Network Events
Volume, USB & Time Machine Events
Apple Music Events
Apple Remote Events
Bluetooth & iBeacon Events
Chromecast & Google Home Events
Computer & Power Events
Screen Events
Misc Events
Scripts can be configured from the EventScripts pane of the preferences. In this pane you can:
• Drag and drop scripts to add or reorder them in the table.
• Use the popup menu to choose the event to trigger the script
• Temporarily disable scripts by unchecking the "Active" checkbox
• Double click a script to open it in the default editor
• Use the contextual menu to apply a 'tag' to a script
You can enable the EventScript server in the server preferences pane. With the server running you can use EventScripts Mobile to trigger scripts on your Mac from your iPhone, iPad or iPod touch by setting them to use the "EventScripts Mobile" event.
The server broadcasts itself only on your local bonjour network.
Tags are useful as they allow you to organise scripts in EventScripts Mobile. You may create, name and select a colour for tags in this preference pane.
Once created tags can be applied to scripts in the main EventScripts preference pane using the contextual menu.
Here we can turn on and off Apple Remote monitoring. EventScripts has two modes for working with Apple Remotes.
Shared mode where EventScripts responds to Apple Remote commands but doesn't prevent other applications (such as iTunes, EyeTV, etc) from responding to them.
Exclusive mode where EventScripts alone will respond to Apple Remote commands.
You can trigger scripts when EventScripts locates iBeacons in your vicinity. The parameters passed to the scripts described the UUID of the beacon, so you can respond accordingly.
EventScripts can trigger scripts based on the proximity of specific Bluetooth devices. Scripts can be triggered when devices are 'found' and 'lost'.
Devices do not need to be paired with your computer in order to trigger events in EventScripts. Devices only need to be 'discoverable' in order to be selected for monitoring but once selected they do not have to stay in discovery mode in order to trigger lost and found bluetooth events.
EventScripts can trigger scripts when it detects motion. To do this it turns on the iSight camera in your Mac and montors the feed for motion.
You can control how sensitive this monitoring is in these preferences.
EventScripts can use the notification center to report on events and scripts executions. You can also enable Prowl notifications here to have notifications forwarded to your iOS device. In addition Pushover notifications are supported via EventScript's AppleScript interface.
There are no special requirements for scripts, but if you want to take advantage of the properties passed by Eventscripts, take a look at the sample scripts for examples.
Remember the properties are only passed when the scripts are trigged by EventScripts. Have a play around yourself, or take inspiration from others.
Finally, note that shell scripts executed by EventScripts are executed by NSTask and as such won't share the user's shell. You may find you need to adjust your scripts accordingly, for example declaring full paths to binaries installed by some package managers.
Free AI Website Maker