Jump to content

tonio

Member
  • Content Count

    8
  • Joined

  • Last visited

About tonio

  • Rank
    Newbie
  • Birthday 02/10/1976
  1. If you read The Daily WTF (http://www.thedailywtf.com/), you might've come across articles by Remy Porter, who includes html comments intended for the readers, and in whose articles you can find a word or phrase you can click on to add unicorns to the page. This Workflow adds a keyword ('remify') which makes the html comments visible, and adds a pink background to the word or phrase which will trigger the unicorns. (I take no credit for the actual JavaScript code... I did tweak it a little bit, but it was copied off some post in The Daily WTF site.) If you're in the Software Development or IT business, and don't know about the site, I recommend it. =) Get the Workflow here: Remify
  2. It'd be nice if the displayed notifications (from the output action) could have a configurable action on click, like many notifications from other applications have.
  3. Currently, the only output actions available are "notification", "clipboard", "large text", and "run script". An option to display the output, either buffered or live, in a window would be nice. I'm currently working on a workflow which has a large amount of output, large enough not to fit in a notification. I'm using Terminal Command to display the output, but it's far from an optimal solution, especially since I can't pipe the output of a script into the input {query} of a terminal command.
  4. I believe you can already do that by selecting the application in Finder, hitting CMD+I (or selecting "Get Info" from the context menu), and entering "bob" in the "Spotlight comments" section. Alfred uses the spotlight comments when matching applications.
  5. It does, and it confirms my fear... the script won't run if the argument is required until you start typing an argument. Is this behavior set in stone? It seems kind of arbitrary to me... in fact, it would make more sense the other way around: if the argument is required, present the options; if it's not, don't present any options unless and until the user starts typing one (since it's entirely valid not to enter an option).
  6. When I've set "Argument Required" on my script filter, I notice that the options list isn't populated until I start typing an argument. With "Argument Optional", it's populated as soon as I type the keyword. Is there any way to force the list to be populated with "Argument Required"? I'd like to show the user a list of possible arguments to pick from, without requiring them to "guess". Or, alternatively (and possibly better), have there be a default argument when none is selected.
  7. Yeah, that was my first thought... but the command I'm running has a lot of output and takes some time to run, which is why I opted for the terminal command action (so the user would see the output as it's being generated). Notification and Large Script clearly won't cut if as output targets, since the output's too long. I guess I could pipe it to a Run Script output which opens up a tcl/tk window, or something like that, with the output... but since Terminal Command fit the bill so well, I'm hesistant to try to hack my way around it. =/
  8. Is there any way to pass a script action's output to a Terminal Command action? I'm basically trying to set a default argument if no argument is set (the keyword's argument is optional) using a script action, and then pass that to a terminal command, but I find I can't "connect" the output of the script to the input of the terminal command action. Am I missing something?
×
×
  • Create New...