Jump to content

Search the Community

Showing results for tags 'feedback'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Alfred 3
  • Make the Most of Alfred
    • Discussion & Help
    • Bug Reports
    • Alfred Feature Suggestions
    • Themes
  • Alfred Workflows
    • Share your Workflows
    • Workflow Help & Questions
  • Alfred v2 Themes
  • Alfred Remote for iOS
    • Alfred Remote Discussion & Help
    • Remote Connection Troubleshooting

Categories

  • Articles
    • Forum Integration
    • Frontpage
  • Pages
  • Miscellaneous
    • Databases
    • Templates
    • Media

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Twitter


Website URL


Jabber


Location


Interests

Found 12 results

  1. Alfred 3.4 (850) type = file is ignored on feedback items when workflow variables are also set via arg (i.e. arg is a JSON-encoded alfredworkflow object). Run the following workflow or build your own Script Filter around the JSON feedback. You can hit right-arrow on the first item with a "plain" arg to access File Actions. File Actions don't work on the second item, however. Demo workflow. Script Filter feedback: { "items": [ { "title": "Path, no vars", "subtitle": "This works with File Actions", "type": "file",
  2. In a multi-step workflow, one where Arg and Var objects separate Filters and are used to pass state from one step to the next, is there any way to go to the previous step without starting over from the beginning? For example, in the Simple Todo List project, when the user types "todo some new task" and presses Enter, the workflow moves to a Filter object, using the output of the initial script filter as input. Is there an easy way to return to the previous state, where Alfred is back on the previous Script Filter with a query of "todo some new task"? I know you can just re-open Alfred and pres
  3. Hey guys, Say I make a Script Filter and link it to 4 script actions that each perform a different function, but each action needs a different input from the Script Filter, and this is where the problem begins, because the "arg" attribute can hold only one value which will work with just 1 of the 4 actions Right now the only workaround to this problem is to give the "arg" attribute a separated list of multiple values, and then each action would need to parse the input and search for its piece of data, but it's too much parsing and splitting involved.. My opinion is that we should
  4. The Format ** This will be an evolving document. Check here for updates and new documentation. ** There is also an XML format example available in Alfred 2 preferences. To see it, open Alfred Preferences, navigate to Workflows. Click the + i nthe bottom right corner of the installed workflows list, select Examples->Script Filter XML format. Result feedback is generated by returning an XML string back to Alfred from a Script Filter item in your Workflow. Script Filters are the only way to pass feedback to Alfred. The following is an example XML string that would be returned to Al
  5. Another quickie from my own personal self, a Things workflow for adding tasks that also, thanks to Alfred's feedback system, searches them. I've been pestering Cultured Code to add this to the Quick Entry panel for ages, since I have a tendency to add one task five times (the number of incomplete "Watch and return Netflix DVDs" tasks I have floating around at any given time is absurd), but now Alfred will handle it for you! Just enter "things" to see a list of all projects, areas, and tasks; keep typing to start entering a task using the plug-in syntax (see below) while searching through pre-e
  6. I've been working on this for a while, and although I've gotten close, I haven't achieved complete success. My goal is basically to have the workflow script generate the workflow. I'd like to have a single top-level keyword and have the script generate everything else dynamically. This mostly works, but implementing Alfred's "waiting for input" subtitle behavior is proving difficult. The closest I've come up with is having the script filter spawn off a separate process to do the long action and return an item with the "waiting" subtitle. The secondary process will update Alfred when the proces
  7. Attached is a simple Wikipedia auto complete workflow. -Download: http://d.pr/f/no3O For those like myself who prefer scripting in Python, the following class makes generating feedback easy -View/Download: http://d.pr/f/GMO8 Example Usage: from alfred import Feedback fb = Feedback() fb.add_item("Hello World", subtitle="Simple Greeting") fb.add_item("Foo", subtitle="Bar", icon="foobar.icon", arg="foobar") print fb Enjoy
  8. Hey there Andrew! I was just rewriting one of my workflows when I had a sudden thought about what could be a neat feedback feature. If it's doable, it might be a little extra interface sugar if a worker of flow could flag a feedback item as the one that's automatically selected. For example, I'm outputting a list of Finder flag colors, but would like to be able to imply that the file is already red. Rather than adding another informational item or something along those lines, it would be nifty if I could add something like default="yes" to the red item. I don't have any kind of sense of how co
  9. This workflow demonstrates several feedback scenarios and can be used as a template for your AppleScript projects. I will maintain an updated copy of this post on my blog: http://www.johneday.com/617/generate-feedback-in-alfred-2-workflows Overview: To generate feedback in Alfred, we use a Script Filter to pass a query to the xml.scpt AppleScript. The script then processes the query and returns a properly formatted XML string containing information for each item to be displayed. After you import the Generate Feedback workflow, launch it with the gf keyword to view my five examples. To
  10. Hello all, I'm looking to write a workflow for a project management system I use. The system has projects. Projects have tasks and milestones. Tasks have subtasks. They have a REST api I've used several times before through both PHP and Python. I'd like to use the feedback mechanisms to let the user start typing a project, and auto-populate as they type. The thing is, I want them to do more things with that project after they've selected it. Here's the flow I'm imagining: User starts typing "foo My Pro" and they see some project appear: "My Project 1" and "My Product Launch" User choos
  11. In file navigation, a preview/info panel is provided to give you a better idea about the selected file. It would be really cool to have a similar method for displaying workflow output. For example, a weather workflow could display a downloaded radar image in that space. A Wolfram|Alpha workflow could display images or text returned from the API. Even the native 'define' function would be more useful, as you wouldn't have to open Dictionary.app to see the entire definition. Thanks
  12. This is best explained with an example: The Amazon Suggest and Google Suggest workflows work fine on fast internet connections. On a slow connection however, it can take a noticable amount of time to load the suggestions. To make those Workflows more usable, i tried to alter them to output the input value as first feedback item, and do that before any connection is even made. The problem now is, that the output of a script is only read once, when the script finished executing. This python script: import time xml = """ <items> <item uid="0" arg="~/Desktop" valid="YES" auto
×
×
  • Create New...