ctwise

I created a workflow inspired by the Parallels controller workflow. It doesn't do screen captures since VMWare requires a username / password to do that, otherwise it's pretty similar. It's on alfpt or you can download it from here: http://tedwi.se/u/d4
 
The following commands are available:
 
 
vm list - Provides a list of VM's and their status (running or stopped). Copies path to clipboard. vm start [nogui] - List the VM's that are currently stopped so you can start them. Optionally, if you add 'nogui' it will start them without showing the VMWare window. vm stop [hard] / vm suspend [hard] / vm reset [hard] - List the VM's that are currently running so you can stop, suspend or reset them. Optionally, if you add 'hard' it will force the action. vm pause / vm unpause - Get a list of VM's that are currently running so you can pause or unpause them. A paused VM counts as running. vm snapshot <name> - Get a list of VM's that are currently running so you can create a named snapshot of a VM's current state, 'name' is not optional. vm ip - List the ip addresses of all running vms and copies the selected ip to the clipboard. The vm _must_ be running vmware tools for this to work. vm revert <name> - revert a vm to the named snapshot.   2013-02-07 - Add icons (cribbed from Jonas Erikson's VirtualBox controller)

http://www.packal.org/workflow/menu-bar-search

Applescript. Create an 'external' trigger in the workflow you're interested in. Give it some name and Alfred will show you the Applescript to run to invoke the trigger. Connect the trigger to whatever you want it to run in the workflow.

Funnel takes text and converts it to some other text by running it through a filter. The filter can be a shell script one-liner or a full script. Anything that takes standard input and outputs to standard out. At the moment, the following filters are implemented:
 
- Base64 - decode - Base64 - encode - AES-256 - decrypt with passphrase 'X' - AES-256 - encrypt with passphrase 'X' - x509 - fingerprint - x509 - hash - x509 - certificate information - Change case - lowercase - Change case - uppercase - Change case - capitalize - Change case - title case - JSON - format - String - reverse - String - format US phone number - Lines - clear bullets - Lines - sorted unique lines - Lines - number lines - Lines - bulletize - Lines - top 10 unique lines - Lines - remove blanks - Lines - unique lines only - Lines - doublespace - Markdown - convert search links to normal links - Markdown - convert to HTML - URL - encode - HTML - encode - Sort IPv4 addresses  
The Funnel workflow is a variant of the preexisting Pipe workflow (http://www.alfredforum.com/topic/1187-filter-clipboard-through-your-favourite-one-liners). I wasn't happy with how the workflow presented options and I didn't want the options sorted by Alfred. I also wanted to bundle some heavier processing scripts, so I created my own version of the workflow from scratch.
 
The workflow can operate on text on the clipboard, on a file whose filename is on the clipboard, on selected text (using a hotkey) or on a selected file (using a hotkey). No matter where the text comes from, it is piped through the selected filter. If the text came from the clipboard or a selection, it is pasted into the active application after being processed. If the text came from a file, the file contents are replaced with the processed text.
 
So, for example, if you select a block of text and trigger the workflow with a hotkey, you can choose 'Lines - bulletize' and the selected text will be replaced with bulleted lines. If you select a JSON file in Finder (or Path Finder) and trigger the file hotkey, you can choose 'JSON - format' and the file contents will be replaced with formatted JSON.
 
Update: As Vitor pointed out, I forgot the link :-) https://github.com/packal/repository/raw/master/com.tedwise.funnel/funnel.alfredworkflow

Funnel takes text and converts it to some other text by running it through a filter. The filter can be a shell script one-liner or a full script. Anything that takes standard input and outputs to standard out. At the moment, the following filters are implemented:
 
- Base64 - decode - Base64 - encode - AES-256 - decrypt with passphrase 'X' - AES-256 - encrypt with passphrase 'X' - x509 - fingerprint - x509 - hash - x509 - certificate information - Change case - lowercase - Change case - uppercase - Change case - capitalize - Change case - title case - JSON - format - String - reverse - String - format US phone number - Lines - clear bullets - Lines - sorted unique lines - Lines - number lines - Lines - bulletize - Lines - top 10 unique lines - Lines - remove blanks - Lines - unique lines only - Lines - doublespace - Markdown - convert search links to normal links - Markdown - convert to HTML - URL - encode - HTML - encode - Sort IPv4 addresses  
The Funnel workflow is a variant of the preexisting Pipe workflow (http://www.alfredforum.com/topic/1187-filter-clipboard-through-your-favourite-one-liners). I wasn't happy with how the workflow presented options and I didn't want the options sorted by Alfred. I also wanted to bundle some heavier processing scripts, so I created my own version of the workflow from scratch.
 
The workflow can operate on text on the clipboard, on a file whose filename is on the clipboard, on selected text (using a hotkey) or on a selected file (using a hotkey). No matter where the text comes from, it is piped through the selected filter. If the text came from the clipboard or a selection, it is pasted into the active application after being processed. If the text came from a file, the file contents are replaced with the processed text.
 
So, for example, if you select a block of text and trigger the workflow with a hotkey, you can choose 'Lines - bulletize' and the selected text will be replaced with bulleted lines. If you select a JSON file in Finder (or Path Finder) and trigger the file hotkey, you can choose 'JSON - format' and the file contents will be replaced with formatted JSON.
 
Update: As Vitor pointed out, I forgot the link :-) https://github.com/packal/repository/raw/master/com.tedwise.funnel/funnel.alfredworkflow

Yet another RDP workflow. This one works exclusively with Microsoft Remote Desktop and lists all of the defined desktops. It works reliably, regardless of the state of the Microsoft Remote Desktop application, this has been a problem with other workflows. You can select from the desktop list or continue typing to filter down to just the desktop you want. It's on Packal already.
 
https://github.com/packal/repository/raw/master/com.tedwise.rdp/microsoft_remote_desktop.alfredworkflow

It still works with Alfred 3. It's likely you haven't enabled Accessibility for Alfred 3.

This probably won't work either then, but you can give it a try:
property newLine : (ASCII character 10) set results to "" set flag to true tell application "System Events" tell network preferences to set locs to every location repeat with loc in locs tell loc set vpns to every service repeat with vpn in vpns if flag is true then set flag to false else set results to results & newLine end if set vpnName to (the name of vpn) as string set results to results & vpnName set results to results & "|" & (kind of vpn) end repeat end tell end repeat end tell results

http://www.packal.org/workflow/menu-bar-search

http://www.packal.org/workflow/menu-bar-search

Settings -> Advanced -> Apps Matching -> Full fuzzy match from word boundary
 
Then PS will match Photoshop.
 
Or, you can create a simple workflow that connects the keyword 'PS' to Photoshop and 'LR' to Lightroom.

The previously released menu search workflow has been universally panned due to the poor performance of the AppleScript that dumps menu contents. The caching of results worked very poorly as a stop-gap. So, I've re-written the menu extraction in Objective-C. It's much faster. The source is here: https://github.com/ctwise/alfred-workflows
 
You can download the workflow directly from http://tedwi.se/u/db
 
To recap, this workflow lets you trigger an application's menu's from Alfred. For example, if you're in iTerm and trigger Alfred, you can type 'm view' to get a list of all menu items with 'view' in the name or that belong to the 'view' menu. Selecting one of the entries triggers the corresponding menu entry in iTerm. In one sense it gives you a command-line to control your applications.
 
The workflow has the beginnings of shortcut key display as well but it's currently disabled due to numerous bugs.
 
Update: 
 
v1.3 - Provide error message when assistive devices isn't checked.
v1.2 - Skip the Safari History and Bookmarks menus. They take too long.
v1.1 - I fixed the bug with Alfred not remembering selections and added AlleyOop support. Download from the same link.
 
Requires OS/X 10.7+.
 
---
 
You need to turn on OS/X assistive device support to allow this workflow to operate. You can find the checkbox in Settings. The settings page looks very different in recent versions of OS/X but the wording for providing access for assistive devices is very similar no matter what OS/X version you're using. Here's an image of the settings from the latest version of Mountain Lion.
 

Yet another RDP workflow. This one works exclusively with Microsoft Remote Desktop and lists all of the defined desktops. It works reliably, regardless of the state of the Microsoft Remote Desktop application, this has been a problem with other workflows. You can select from the desktop list or continue typing to filter down to just the desktop you want. It's on Packal already.
 
https://github.com/packal/repository/raw/master/com.tedwise.rdp/microsoft_remote_desktop.alfredworkflow

The previously released menu search workflow has been universally panned due to the poor performance of the AppleScript that dumps menu contents. The caching of results worked very poorly as a stop-gap. So, I've re-written the menu extraction in Objective-C. It's much faster. The source is here: https://github.com/ctwise/alfred-workflows
 
You can download the workflow directly from http://tedwi.se/u/db
 
To recap, this workflow lets you trigger an application's menu's from Alfred. For example, if you're in iTerm and trigger Alfred, you can type 'm view' to get a list of all menu items with 'view' in the name or that belong to the 'view' menu. Selecting one of the entries triggers the corresponding menu entry in iTerm. In one sense it gives you a command-line to control your applications.
 
The workflow has the beginnings of shortcut key display as well but it's currently disabled due to numerous bugs.
 
Update: 
 
v1.3 - Provide error message when assistive devices isn't checked.
v1.2 - Skip the Safari History and Bookmarks menus. They take too long.
v1.1 - I fixed the bug with Alfred not remembering selections and added AlleyOop support. Download from the same link.
 
Requires OS/X 10.7+.
 
---
 
You need to turn on OS/X assistive device support to allow this workflow to operate. You can find the checkbox in Settings. The settings page looks very different in recent versions of OS/X but the wording for providing access for assistive devices is very similar no matter what OS/X version you're using. Here's an image of the settings from the latest version of Mountain Lion.
 

Short answer: http://www.packal.org/workflow/menu-bar-search
 
Long answer:
1. Use the menudump command in the above workflow to dump the menu structure of the app you're targeting (--help for details)
2. Use the output to determine the Applescript line to target the menu item, e.g.,
 
tell menu item "Check For Updates…" of menu "iTerm2" of menu bar item "iTerm2" of menu bar 1
    if (it exists) then perform action \"AXPress\"
end tell    You can look at the execute.scpt file in the above workflow for more details.

An argument is the information typed after a keyword. For example:
 
mysuperspecialkeyword does stuff
 
Your keyword here is 'mysuperspecialkeyword'.
 
Your arguments are 'does stuff'.
 
If you create a keyword that shows weather where you live then it won't take any arguments - you type 'weather' and you're done.
 
If you create a keyword that shows weather for a given zip code, you need arguments, 'weather 11223'.

Thanks to Alfred's brand new method of triggering, yes, you can do this now. I have a text processing workflow which I'm going to have to update because of this. I didn't even realize it until you brought this up - so, kudos.
 
Here's the script snippet:
 
on alfred_script(q)
    tell application "System Events" to keystroke "c" using command down     delay 0.3     do shell script "pbpaste" end alfred_script   This will send the current application a ⌘C to copy whatever text is selected. You need to pause at that point for the app to do the copy and put the text on the pasteboard. After that you can do what you want with the copied text. In the above example I just dump it onto stdout.

Known problem - https://youtrack.jetbrains.com/issue/IDEA-114252 -- https://bugs.openjdk.java.net/browse/JDK-8071668
 
It's a Java issue. You can use the latest JDK (8u60) or their custom JDK they bundle with IntelliJ. There's also a possible workaround in the first link. Basically Java caches the pasteboard when it gets focus. If focus doesn't leave the app it doesn't recognize when the clipboard manager changes the pasteboard.

I need everyone's help. Microsoft's Remote Desktop app is barely scriptable by throwing keystrokes at the app. That works poorly and breaks constantly with updates. We need that app to be scriptable in order to control it reliably. Microsoft doesn't want to implement scripting support. But they have a mechanism to vote for feature requests. Please follow the below link and vote the max (3 votes) for the feature:
 
https://remotedesktop.uservoice.com/forums/287834-remote-desktop-for-mac/suggestions/9280833-allow-the-application-to-be-controlled-with-apples
 
Even if you don't use Remote Desktop I'd appreciate the help.

You can do it yourself right now. Preferences -> Features -> Contacts -- click on Phone and pick 'Pass to URL Scheme'. In the URL field, enter 'tel://{query}'. Now when you press enter on a contact phone number it'll open the call dialog. You _do_ have to press the Call button to initiate the call though.

I'm a little baffled as well, but I bought it to give Andrew a little more money to keep supporting software that I love and use every day and to test workflow integration with Remote. Who knows, maybe I'll find a good use case for it.

Most of the workflows that deal with large amounts of text use the pasteboard to pass the text around. Stdin would be awesome, but the pasteboard is a workaround.

The previously released menu search workflow has been universally panned due to the poor performance of the AppleScript that dumps menu contents. The caching of results worked very poorly as a stop-gap. So, I've re-written the menu extraction in Objective-C. It's much faster. The source is here: https://github.com/ctwise/alfred-workflows
 
You can download the workflow directly from http://tedwi.se/u/db
 
To recap, this workflow lets you trigger an application's menu's from Alfred. For example, if you're in iTerm and trigger Alfred, you can type 'm view' to get a list of all menu items with 'view' in the name or that belong to the 'view' menu. Selecting one of the entries triggers the corresponding menu entry in iTerm. In one sense it gives you a command-line to control your applications.
 
The workflow has the beginnings of shortcut key display as well but it's currently disabled due to numerous bugs.
 
Update: 
 
v1.3 - Provide error message when assistive devices isn't checked.
v1.2 - Skip the Safari History and Bookmarks menus. They take too long.
v1.1 - I fixed the bug with Alfred not remembering selections and added AlleyOop support. Download from the same link.
 
Requires OS/X 10.7+.
 
---
 
You need to turn on OS/X assistive device support to allow this workflow to operate. You can find the checkbox in Settings. The settings page looks very different in recent versions of OS/X but the wording for providing access for assistive devices is very similar no matter what OS/X version you're using. Here's an image of the settings from the latest version of Mountain Lion.
 

I just looked through the programming guide for LaunchBar 6 "actions" which are their equivalent of workflows. Alfred, in general, has more comprehensive workflow support (not even counting the GUI layout tool), but LaunchBar 6 has some features it would be nice to see in Alfred:
 
- Scripts can be marked to be killed if they don't return before the next keypress, e.g., user types 'A', script searches the internet, user types 'B', script is killed and re-run with 'AB'     This is an overall feature that's been requested many times but I don't think anyone actually mentioned killing the currently running script.   - Scripts support either 'strings' or 'paths'     I believe a script that takes a path gets path completion support in the LaunchBar entry box.   - Scripts can return a 'string', a 'path' or a complex result     LaunchBar assumes defaults for everything if your script just returns a string or a path instead of XML, JSON, etc.   - Environment variables are passed to the script w/various paths and information about the state of the option key, command key, etc.   - LaunchBar can accept script output in JSON, XML or a property list XML     I don't care about property list XML, but I would love if JSON was an option.   - Items returned by a script can include a quicklook URL   - Items can indicate another script to run to get the next 'level' of items, e.g., a multi-level menu - Items can directly list out the next 'level' of items     Various Alfred scripts now have hacks that "re-call" the script and mimic multiple levels of results. LaunchBar bakes it into the workflow model.   - LaunchBar actions are code signed   - LaunchBar supports using JavaScriptCore as a scripting language   - Scripts can marked to be initiated by LaunchBar but LaunchBar immediately returns (doesn't wait for output)    

You can do it yourself right now. Preferences -> Features -> Contacts -- click on Phone and pick 'Pass to URL Scheme'. In the URL field, enter 'tel://{query}'. Now when you press enter on a contact phone number it'll open the call dialog. You _do_ have to press the Call button to initiate the call though.