rice.shawn

I'm just chiming in to +1 the recommendation for the Spotify Mini Player workflow that Andrew mentioned. It's incredibly well polished and amazing. Vdesabou did an amazing job with it and keeps actively developing it.
 
Here it is on Packal, too: http://www.packal.org/workflow/spotify-mini-player.

Can you try to launch the Packal "GUI"?
 
Just try that without the "packal setup" and the regular argument "packal" with no subargument. It should be the first option, and it will work as long as you're running either Mavericks or Yosemite.
 
Let me know what happens.

I had a similar problem with two versions of Radium in Applescript the other day.  You can get the id as described here: http://www.macosxautomation.com/applescript/features/appobject.html
 
Just open Script Editor, and run the following one-liner:
 
get id of application "FakeApp"
 
Script Editor will ask you "Where is FakeApp?" and open a list of installed apps.  Select the correct version of PowerPoint there and you'll get its id.
 
You can then address it 
 
tell application id "com.microsoft.PowerPoint" (or whatever the actual id is)
 
instead of
 
tell application "PowerPoint"
 
 
 
 
Applescript is weird.

Here's a simple workflow that lets you use Alfred Remote (https://itunes.apple.com/app/alfred-remote/id927944141) to control your powerpoint presentations.
 
Find it on Packal: http://www.packal.org/workflow/powerpoint-remote.
 
Note: you need Alfred 2.6 to use this workflow. If you install this workflow on a version previous to v2.6, then you'll need to reinstall it after you install 2.6 in order to have the remote page available.
 
 
The icons are a bit awkward, but here's a screenshot of the remote page.
 
 

For TextEdit it's fairly easy:
 
1: Create a new blank workflow
2: Add three hotkey triggers, one for each color you want
3: Add three RunNSApplescript Actions, again, one for each color.
 
Now, in each of the RunNSApplescript Action boxes, you will want to paste this:
on alfred_script(q) tell application "System Events" to tell text area 1 of scroll area 1 of window 1 of process "TextEdit" to if exists then set {x, y} to value of attribute "AXSelectedTextRange" if x ≤ y then tell application "TextEdit" to set color of document 1's characters x thru y to {65535, 0, 0} end if end alfred_script NOTE:  That I also copied the included 'alfred_script', so if you just copy and paste the above into the window, make sure you overwrite the others already in there.
ALSO NOTE:  The color in brackets for the above is RED as the format is {RED, GREEN, BLUE} and the initial value is all red, and zero green and blue.
For the green NSAppleScript {0, 65535, 0},
For the blue NSAppleScript {0, 0, 65535}
 
Then, connect your hotkey boxes to the appropriate NSAppleScript Boxes.

No, it’s for sure; it tells you right there.
 

Still has got nothing to do with Alfred. A quick google search shows you a ton more people with the same problem, including that very app. There are also a bunch of solutions. Try this.

Following Tyler's note and to agree, it's not available "yet". Alfred Remote is the result of a lot of time and effort on Andrew's part and certainly couldn't be considered a "rushed release". Software is an iterative process. Every software package has updates, fixes, and new feature additions. If any software product was withheld until every possible feature, every fix, every bug, every idea was implemented, we'd never see any of them. That being said, this is only the beginning for Alfred Remote. Andrew has lots of other ideas planned.

You could just use Ctwise's Network Info workflow for that.

When asking for help, be verbose. A link back to the application’s website is the minimum. Opening the website it’s not even possible to tell at a glance if it’s even available for OS X, as it seems to be mobile only. Many people would be able to give you a hand with this, but we shouldn’t have to do all the research. The more steps you make people go through, the less help you’ll get.

For whenever the new version of the Alfred Bundler gets done, it includes dynamic icon sets (https://shawnrice.github.io/bundler-docs/icons.html).
 
But... you can actually use these now-ish. You can preview / download the icon sets in any color you need: http://icons.deanishe.net/ or the mirror: http://icons.shawnrice.org/.
 
Granted, these are only flat icon sets, but they're still something.
 
(Note: Dean and I got especially excited about the idea because we both suck at icon creation but have a tendency to write a lot of workflows. Dean wrote the entire icon server. He rocks.)

I'm just chiming in to +1 the recommendation for the Spotify Mini Player workflow that Andrew mentioned. It's incredibly well polished and amazing. Vdesabou did an amazing job with it and keeps actively developing it.
 
Here it is on Packal, too: http://www.packal.org/workflow/spotify-mini-player.

That's a good point -- I can envision a lot of scenarios where a toggle would make sense if you have a screen in front of you, but where separate buttons are preferable where the state might be unknown.

I actually already have a note to consider adding installable "icon sets" into Alfred which would then be selectable in the image pickers, I think this would be a great addition

You could just use Ctwise's Network Info workflow for that.

Alfred Remote is more like a sidekick than a remote in the sense that you're thinking of. It gives you easier access to a lot of things while you're at your computer.
 
You can make it more of a remote in the sense that you're thinking of, but you need to write workflows that will handle each part of the operation.

If you want to access the volume, you might consider using AppleScript to adjust the volume directly rather than doing keystrokes. Here's a reference that you can use for that.

A lot of Alfred workflows and commands have options when certain keys are pressed.  These keystrokes can be sent from Alfred Remote with a bit of Applescript.  e.g. to hold and release the Control key, add the following:
 
Alfred Preferences > Remote > System Commands (or wherever you want on your remote) > + > Run Script > language: /usr/bin/osascript
  then paste in the following short Applescript: tell application "System Events" control key down end tell Name this item "Hold Ctrl" but BEFORE YOU TEST IT add a second command following the same procedure:
tell application "System Events" control key up end tell Name this 2nd item "Release Ctrl".
 
Now you can test it and make sure it works.  If you test the first script before adding the second, you will end up with a practically unusable computer b/c the Control key will be down and you will have no way to release it.  I found this out the hard way and had to reboot.
 
IMPORTANT - this does not work with the Option key for reasons that are unclear.  You can create an Applescript to hold the Option key down, and it will work, but the corresponding script to release does not work, and you'll be forced to reboot to get your keyboard working normally again.

I've been having all kinds of problems with the network on Yosemite, especially after sleeping.
I think there's just something wrong with Yosemite.

I'm not sure what you're getting at here either. Why do you need to modify proxy.scpt? Two things on this:
 
(1) Keep your code and your data separate. If you are modifying a script to be run, then you should consider it data. Keep the original (template) in the workflow directory, and then all modified copies should be in either the data or the cache directory.
 
(2) If you're using Python in other places, then you should try to stick with it as much as possible. But if you want to use a "Choose From List" AppleScript function, then you could also try to call that from Python. Basically, the "Choose from List" AppleScript is just a string that you can invoke via the shell via osascript, so you use can Python to construct the string and call as Python would call any shell script.
 
(3) AppleScript prompts can be cool, but I always try to keep my use of them to a minimum. If your "Choose From List" comes up with just a couple (say fewer than 9) options, and you want to select only "one" option, then you could always keep everything in a script filter and have the user choose from a list of results there.

So far, I've identified just which "run script" workflow objects are which via the keyword or script filter they're attached to. But, some of my internal workflows are getting fairly "congested" with quite a few "run scripts" so that I have to open them sometimes in order to remember what they are.
 
I would love it if we could set a sort of internal label that would appear on the workflow canvas but affect nothing else.

I'm not exactly sure what happened, but the site started to do things like that a little while ago. I've been just going on and fixing it manually. Something must have happened when I upgraded some module (the Packal site is a Drupal 7 installation).
 
Over the last few weeks, however, I've been experimenting with rewriting the site from the ground-up in ways that will make any of these issues moot.
 
For now, I went in and re-uploaded the icon and flushed the caches, so everything should look right.
 
Sorry about the bugs.

Hm. Can you check a few things for me?
 
(1)
 
Open the GUI for the Packal updater and manually update the manifest. Then, select the update menu in that GUI and tell me if the update is still pending. If so, then...
 
(2) Open the workflow preferences and select "Spotifious"; then ctrl+click on it and select "Show in Finder"; then open the "packal" folder, and then open "package.xml" What are the values there for "version" and "updated"?

But I have gone back willingly.

Heh. Didn't realise there were that many.
 
SIGXFSZ: "File size limit exceeded". More like "Epileptic fit at keyboard".

Here's Vítor's Ruby code as PHP:
$keyword = strtolower( "{query}" ); $urls = [ 'linux' => 'http://en.wikipedia.org/wiki/Linux', 'ruby' => 'https://www.ruby-lang.org/' ]; if ( array_key_exists( $keyword, $urls ) ) { exec( "open {$urls[$keyword]}" ); } The only addition is a check to make sure that the array key exists before opening it.