Tyler Eich

To put the current answer into Alfred's search, try typing an '=' at the end of your calculation (e.g. '42/7=' or '=sin(60)=' for the advanced calculator)
 
I do like the parentheses idea, though. I hate moving my cursor just to wrap in parentheses.
 
+1 for a smarter parser
 
Cheers

I noticed that in OS X 10.9 Mavericks, notifications can use custom icons. iTunes 11.1.2 does this when sending 'Now Playing' notifications, using the album artwork as the primary image.
 
It would be great if workflows could specify custom icons to use in a notification. For example, my Colors workflow could display an image of the color that has been copied.

I found my workflows stored in ~/Library/Application Support/Alfred 2/Alfred.alfredpreferences/workflows/   They will be randomly-named folders, not files   You may also want to copy these folders to your new system: ~/Library/Application Support/Alfred 2/Workflow Data ~/Library/Caches/com.runningwithcrayons.Alfred-2/Workflow Data These are, respectively, the cache and data folders used by your workflows.   Cheers

Trash Workflow
 
This should do what you want, except I chose 'trash' as my keyword instead of 'delete'. Hope this helps

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

Under Alfred Preferences > General > Where Are You:, try changing the country to 'United Kingdom'

Awesome!
Please let me know if you have suggestions

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

To any who may be interested: Percentage calculator workflow
 
Type "100 + 10%", get "110" as the output. It emulates the behavior of a 4-function pocket calculator.
 
Enjoy

I doubt this will completely remedy your issue, but if you set Alfred to use 'Complete fuzzy matching from word boundary' ('Advanced' Tab > 'Apps Matching'), 'adw' will match 'Adobe DreamWeaver'.

Check out the 'Setup fallback results' button toward the bottom of 'Features > Default Results'

Warning: You may already be aware of the following information!
Cmd-Tab is the hotkey for OS X's built in app switcher (you probably knew that)  If Word (or any other application) is open, typing 'Word' (or any other application's name) into Alfred will bring that app to the front. There are a few ideas buzzing around for window re-sizers and organizers. For example, this workflow is a port of the Layout's extension for Alfred v1.x (check out this post for the contextual discussion). It might satisfy your window-organizing needs 

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

I apologize for any misunderstandings, but Alfred Version 3 has not yet been released to the public. "On the way" indicates that it is not yet finished — though you can bet Andrew and Vero are working like mad to get it out the door!
 
To clear a few things up:
The email you received was not malicious. In fact, giving you the opportunity to purchase the Powerpack at a 10% discount has saved you money Since you just purchased a Powerpack license, you will receive a free upgrade to v3 when it's ready. You have immediate access to Alfred 2 (which is already awesome) and a free license to use the next major version. You have access to two versions of Alfred for the price of one license Vero is a single person who handles license inquiries and support, and Vero needs to sleep. Please be patient, as I'm sure she'll be waking up to many, many emails  Finally, welcome to the forums! If you have any further questions, please ask! There are plenty of very smart people here who gladly share their knowledge with new users 

Yup, that's exactly it!
 
 
Don't get me wrong, I also feel icky running an Alfred search via AppleScript, but I feel that, on balance, it's preferable to External Triggers due to their funky UX. Adding the keyword to the env vars would be a simple way (in terms of effort for Andrew and the current execution model) to eliminate the fairly substantial risk of everything breaking because a user changed the keyword. It's a stopgap while we wait for that first-class way of telling Alfred what to display next.
 
I also like your idea of Alfred maintaining a stack. It's just that I think if Alfred is going to start tracking workflow state (which maintaining a stack would involve at some level, unless it's just doing some parsing of {query} for you), it may as well take it a bit further, so the workflow itself doesn't also have to worry about state (in the common case). As you say, stateful programming sucks, so clearly it's better to leave that to Andrew. That's what we pay him for
 
In terms of the execution model, your suggestion isn't a huge leap. It would make the UI a lot cleaner for users, but not change much for developers. What I'm suggesting would change the execution model significantly (although it shouldn't break existing workflows), but also provide significant benefits for developers.
 
In terms of effort for Andrew, neither is insignificant. I suspect the most significant component would be getting the UI for the breadcrumb navigation/stack right.
 
 
Both should work equally well in situations where the stack = the argument, such as directory trees. If you're working with API or database data, where every node has an ID, you'd want to pass the ID and wouldn't care about the stack (if Alfred were taking care of it for you).

In reply to Dean:
 
Your last explanation clicked for me
 
Let me try to explain what I see between our two approaches:
 
Tyler's:
UI sugar on top of the already-available workflow capabilities (delimiters, submenus) Developer is in the same position as previously Script filters act statefully, using tab-delimited inputs to rebuild state for each execution Pros:
Prettier UI Simpler to back out of an action (just remove the last entry from the stack) Cons:
Stateful programming sucks Developers receive no real help with control flow  
Dean's:
Send output directly to an (a.) action that does a thing (b.) script filter that return more options Each item is responsible for declaring where it should be sent if actioned No action or script filter needs to know how the last step got its result, it only needs the result Actions and Script Filters are labelled, basically eliminating the need for external triggers to pass data within a workflow Pros:
Stateless components Much simpler control flow Cons:
Could require significant rethinking of the Trigger/Input/Action/Output paradigm (may also be a Pro) To allow undo/back out, Alfred needs to maintain a stack of previous actions and the outputs sent to them  
I have an intuitive sense that each solution has a different optimal use case, but I haven't thought too hard about it. Maybe my idea would be better suited to simple drill-down navigation, while yours is better suited to control flow between functional components.
 
Either way, I like what I'm understanding about your solution. It's as big of a leap in capability as Alfred 2 was to Alfred 1.
 
To me, it sounds like script filters have outgrown their implementation. From what I'm seeing, a script filter does not always need to have a keyword, nor does it always make sense to do so.
 
It sounds like people want a first-class way of telling Alfred which UI to display next. The current solution (using Applescript to call an External Trigger or to populate Alfred with a keyword) is sub-optimal. I don't know about you, but I feel dirty every time I type osascript -e 'tell application "Alfred 2" to search "keyword"'.
 
I can see benefit to having the keyword in the environment if you want a quick fix that's as dirty as Applescript, but not if the system itself were built to handle this interaction better. If workflow objects had developer-specified labels, the keyword chosen by the user would be irrelevant.

What about a new value for the type attribute? Something like type="category". When actioned, the icon of the category is placed into Alfred's UI similarly to the way External Triggers do.
 
Example of how it would work:
 
User is activating a workflow that uses a script filter to drill into a folder structure to find a specific file
 
User activates script filter with "drill alpha-folder"
User selects item with:
type: "category"
arg: "/alpha-folder"
icon: "alpha-icon.png"
 
Alfred places "drill-icon.png" and "alpha-icon.png" into the left part of the UI (as occurs for External Triggers)
Alfred sends "/alpha-folder" as query to script filter
​Script filter responds with results from /alpha-folder
 
User selects item with:
type: "category"
arg: "/bravo-folder"
icon: "bravo-icon.png"
 
Alfred places "bravo-icon.png" above/next to "alpha-icon.png" to indicate hierarchy (at some reasonable point, icons collapse instead of stacking at full width)
Alfred sends "/alpha-folder [tab] /bravo-folder" as query to script filter (tab separated, similar File Actions)
Script filter responds with results from /foo-folder/bar-folder
 
User presses delete key
 
Alfred removes "bravo-icon.png" from UI stack
Alfred sends "/alpha-folder" as query to script filter
​Script filter response with items from /alpha-folder
 
User selects item with:
type: "file"
arg: "/alpha-folder/charlie-name.txt"
icon: "charlie-icon.png"
 
Alfred sends "/alpha-folder/charlie-name.txt" to the next action
Action does whatever it does, just like always…
 
Let me know what's good, bad, and/or ugly about this solution. I'm very interested to hear how other people would approach this issue, especially those with more experience developing hierarchical workflows.

To any who may be interested: Percentage calculator workflow
 
Type "100 + 10%", get "110" as the output. It emulates the behavior of a 4-function pocket calculator.
 
Enjoy

Trash Workflow
 
This should do what you want, except I chose 'trash' as my keyword instead of 'delete'. Hope this helps

No, it isn't. 100 plus 10% is 110. And 6% of 500,000 is 30,000.
You're asking a different question, namely "what figure, when 10%/6% is deducted, leaves me with 100/500,000".

Hi
 
If I load up the clipboard/snippet viewer it opens up and that's fine. At the top of the list I can open up a list of available snippets or I can click on one of the items in the list of clipboard items if I wish to. However, if I open the list of available snippets and then decide that I want to go back to the list of clipboard items instead how do I do that? I've tried all the keys I can think of to no avail and at the moment I have to press the esc key to close the pane and then toggle Alfred again. I'm sure there is another way of going back to the opening list that I have failed to find.
 
Thanks,
 
Q

This is a limit imposed by UNIX, not Alfred, but the error message shown is slightly confusing, and there should be a way to overcome this issue.
 
Right now, selecting more than exactly 260527 characters on my system and using it in an Alfred workflow (with the Argument:'selection in OS X' setting) as "{query}" will throw an error.
You can see your system's bash argument character limit with:
getconf ARG_MAX Alfred should allow a way to pass the selection as stdin instead of a quoted and escaped string, otherwise there is no way around this hard limit, and Line-Counting workflows, etc. are useless for larger bodies of text.
 

^ Confusing error message when selecting too much text.
 

^ A workflow example that would trigger this.
 

echo "{query}" > .wordcount echo "Characters: "$(wc -m < .wordcount)"  Words: "$(wc -w < .wordcount)"  Lines: "$(wc -l < .wordcount) rm .wordcount

I definitely agree with this... I've added a note to look into this for the future

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

So, this popped up over in the help forum, but this is a better place for it to solicit feedback, methinks.

Currently, Alfred allows you to specify alternate subtitles for the result items returned by Script Filters, so that you can let the user know which action would be run.

Looks like this:
<item arg="/path/to/Ideas.txt" uid="/path/to/Ideas.txt" valid="yes"> <title>Ideas.txt</title> <subtitle>Open file</subtitle> <subtitle mod="cmd">Reveal file in Finder</subtitle> <subtitle mod="alt">Trash file</subtitle> </item> Whereby the Script Filter is connected to three different Actions.
 
The suggestion is to turn the alternate subtitles "inside out" and add a <mod> (or <alternate>) tag that can override not just the subtitle, but any of the item's parameters (that make sense):
<item arg="/path/to/Ideas.txt" uid="/path/to/Ideas.txt" valid="no"> <title>Ideas.txt</title> <subtitle>Search in Ideas.txt</subtitle> <icon type="fileicon">/path/to/Ideas.txt</icon> <mod key="shift" valid="yes" arg="/path/to/Ideas.txt"> <subtitle>Open this file</subtitle> <!-- the super-smart workflow has figured out the default app for this filetype --> <icon type="fileicon">/Applications/Sublime Text.app</icon> </mod> <mod key="cmd" valid="yes" arg="/path/to/Ideas.txt"> <subtitle>Reveal in Finder</subtitle> <icon type="fileicon">/Applications/Finder.app</icon> </mod> <mod key="alt" valid="yes" arg="/path/to/Ideas.txt"> <subtitle>Trash</subtitle> <icon type="icon">trash.png</icon> </mod> </item> This would have a few advantages:
It's possible to set an item to invalid for if, say, you want to require an additional argument by default, but override that in alternate actions. Currently, an action is always valid or never valid (this was the starting point). You can change not just the subtitle, but also the title and/or the icon, providing more and better contextual information (don't forget, some users turn off subtitles) You can change the arg. This means you can avoid a plethora of Run Scripts/Open URL actions and instead generate alternate URLs (e.g. to different search engines) right in your Script Filter and connect it to just one Open URL action. The same goes for copying different representations of data (e.g. colours, emoji or other non-ASCII text) to the pasteboard. (This would also require Alfred to allow multiple connections to the same Action/falling back to the "bare" action if there isn't another connection for the modifier) By avoiding hard-coded actions, it makes it easier to allow users to configure workflows without having their changes overwritten by a workflow update (which necessarily happens to any user-added actions and connections in a workflow) It wouldn't make sense to be able to override all of an item's options (e.g. uid, copy text and large text).
 
It strikes me (and Florian) as a powerful addition.
 
What do you think?