Tyler Eich

Tyler's so smart, he's my hero Thanks dude

Hello! 
 
Could you try running the 'setappid.php' file in your Terminal?
Right click on the 'Wolfram|Alpha' entry and click 'Show in Finder'. Find 'setappid.php' in the resulting Finder window. Open Terminal and type: php -f <drag the setappid.php file here> -- 'test' (do not include < or >) Hit return and let me know what comes out  Thanks for your patience 

Thanks Tyler! I searched but didn't see that thread!

Colors v2.0.0
 
Get it from Packal (Recommended)
 
Quick Summary:
This workflow can process and convert all CSS color formats and several Objective-C formats, namely NSColor (calibrated and device) and UIColor. It also provides an interface to the OS X color panel for easier color manipulations.
 
It's written in native code (i.e. it's really fast).
 
Quick Preview:

You can find a full description on Packal.
 
Direct download • source code on Github

Other workflows (like the Wikipedia, Amazon, and Google Suggest) use different APIs than Wolfram|Alpha. You see, Wikipedia, Amazon, and Google are very quick to respond when you send a request to their servers. The Wolfram|Alpha API is a bit sluggish, mainly because it does more processing of your request and sends real answers back (instead of suggested search queries).
 
All of this adds up to a notable lag between your keystrokes and the appropriate results. I wish I could do something about this, but I can't 
 
Hope this helps 

Perfect - just the answer I was looking for.  Thank you!

There are many workflows that need configuring before being used (mainly the ones that need some type of account login/setting). However, there's no practical way of implementing that via Alfred. I find making users edit settings manually or having a separate option that'll always show in the results, for an action you typically only run once, to be non-optimal experiences.

For this purpose, I have two workflows that employ a script filter, that does something like this
if (settings_file_exists) show xml with text — “configure your account” arg — <some_string_to_let_the_script_know_it_is_a_configuration> {query} else show xml with text — “do your action” arg — {query} Even though this works well with DownVid, since only the configuration is needed (the else part takes no input); with PinAdd, not so much.

The problem here is that since PinAdd takes {query} as the xml’s arg, if your computer is slow at the moment or you type too fast and then press return, Alfred will act immediately, without waiting for the xml to rebuild/re‐output with the updated {query}. Realistically, I only need the xml to build once, and then take the full, correct, untruncated {query} as the argument, where requested.

Perhaps script filters aren’t build around this idea, but there is clearly a need for it, as currently you only get one of the worlds — either you can show different options depending on the case but you can’t really type some action to be passed through (script filters), or you can get the action perfectly but without having options (keyword input).

My suggestion is then, perhaps instead of creating more options in script filters for specific cases, maybe create a separate category like “keyword filter” or “keyword conditional” or some better name. What this would do is allow you to specify some code to run as soon as you enter its name (much like script filters do), but this code would run only once, outputting some predefined xml, and would take a full argument passed through, much like the keyword input.

When I do a file search and action a folder (opening it in Finder), Alfred learns and moves it closer to the top of the results. However, if I navigate into that folder (by pressing command+down) within Alfred, it doesn't seem to learn.
 
I usually just use Alfred's file navigator rather than opening folders in Finder, so it's a bit counter-intuitive to have to open it in Finder first for it to be placed near the top of the results. It'd be nice if Alfred could learn when you navigate into a folder.

I know exactly what you mean! I wish the script would run faster, too. Wolfram|Alpha is a bit sluggish, and launching the script with only a few characters is wasteful.
Right now, the workflow waits until at least three characters have been entered (as suggested by David Ferguson). I would love it if I could throttle the script, but I can't. Andrew might add a feature like this later on; it has been suggested by a few people (http://www.alfredforum.com/topic/535-throttle-script-filters/).
Thanks for the feedback, and I'm glad you like it!

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.
 

Awesome, thanks for sharing Tyler.

I was working on converting this very same script this morning, so I thought I'd better come and check I wasn't reinventing the wheel. And low and behold I find this post.
 
Excellent work that man, excellent work!

I converted David Ferguson's Wolfram|Alpha extension to a workflow (and made some tweaks along the way  )
 
It requires you have an AppID of your own (get one here). Note: Make sure you wait a few minutes before entering the code; Wolfram|Alpha's servers seem to take a moment to register the AppID.
 
It provides feedback with the answer and input interpretation. If you action an item, it will output all the available information to Growl. Pressing ⌥↩ will copy the answer to the clipboard; ⌘↩ will open your query in Wolfram|Alpha (in the default browser).
 
Here's a picture of the workflow editor:

 
Here's what it looks like in action:

 
Hope you like it!
 
Download Here
 
Update (May 15, 2013): Fixed another bug that prevented saving of AppID
 
Update (March 5, 2013): Fixed bug that prevented the workflow from saving AppID on certain setups
 
Update (Feb 25, 2013): Fixed garbled text issues, added 'Selection is OS X' argument to hotkey

Pastel Sky: Download
 

 
Pastel Grass: Download
 

 
Pastel Orange: Download
 

 
Pastel Peach: Download

This should fixed in 2.0.3

Great workflow! Thank you so much Tyler and everybody involved! 

This is actually something I've recently started to look into, I'm likely going to move that back from Noted into Bugs at some point

Hey,
Is there any way to force Alfred to use the workflow keyword, or give it precedence? I'm using e.g. the Colors workflow by Tyler Eich and the keyword is just 'c', but when I type only 'c' I get hundreds of hits, from bookmarks, contacts, etc. Is there a hotkey/modifier/preference to call the workflow above all?
 
Thanks!

After playing around for a bit I discovered that the script runs exactly as intended if included via the NSApplescript action. Perhaps due to what Andrew refers to as "security" restrictions on osascript? http://www.alfredforum.com/topic/1862-nsapplescript-vs-run-script/?p=9838
 
 
EDIT: Turns out there's more to it than that. Here's what I did, and what I found.
 
Ran via Run Script - Behaviour still not as expected
Ran via NSApplescript - Behaviour still not as expected
Ran once via NSApplescript with caching - Behaviour still not as expected
Ran a second time via NSApplescript with caching - Works perfectly
Ran a bunch more times via NSApplescript with caching - Works perfectly
Restart Alfred and run again - Behaviour not as expected the first time
Run a bunch more times - Works perfectly
 
So once the script has been cached it appears to work as expected.

Colors v2.0.0
 
Get it from Packal (Recommended)
 
Quick Summary:
This workflow can process and convert all CSS color formats and several Objective-C formats, namely NSColor (calibrated and device) and UIColor. It also provides an interface to the OS X color panel for easier color manipulations.
 
It's written in native code (i.e. it's really fast).
 
Quick Preview:

You can find a full description on Packal.
 
Direct download • source code on Github

I converted David Ferguson's Wolfram|Alpha extension to a workflow (and made some tweaks along the way  )
 
It requires you have an AppID of your own (get one here). Note: Make sure you wait a few minutes before entering the code; Wolfram|Alpha's servers seem to take a moment to register the AppID.
 
It provides feedback with the answer and input interpretation. If you action an item, it will output all the available information to Growl. Pressing ⌥↩ will copy the answer to the clipboard; ⌘↩ will open your query in Wolfram|Alpha (in the default browser).
 
Here's a picture of the workflow editor:

 
Here's what it looks like in action:

 
Hope you like it!
 
Download Here
 
Update (May 15, 2013): Fixed another bug that prevented saving of AppID
 
Update (March 5, 2013): Fixed bug that prevented the workflow from saving AppID on certain setups
 
Update (Feb 25, 2013): Fixed garbled text issues, added 'Selection is OS X' argument to hotkey

The Alfred Extras site, from my understanding will be more of a curated site and not a full repo of all available workflows. Currently, alfredworkflow.com, APM (in beta), or searching the forums are the best method for finding a full list or searching for potential workflows for Alfred 2

Hey ;D ! 
 
Awesome Workflow!
 
I added UIColor code format ~ !
 
If you want to add to the main Workflow, here it is: http://db.tt/ZvJgGnof

I'd never thought of this before, but it's a great idea 
 
Sometimes I know I'll need Alfred for something. I hit Cmd-Space as a reflex, but then I realize I'm not ready to use him; I have to close Alfred, get what I needed, and open him again. Or sometimes I need to look at Alfred while performing another task, but he disappears because he doesn't want to get in my way 
 
It's a small feature, but it could save a few occasional headaches

The reason is that some workflow requires a bit of time to run. and some of them related to monitoring, notes and tasks can be useful to just pin on the top for a while.