Jump to content

Search the Community

Showing results for tags 'Workflows'.



More search options

  • 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

Categories

  • New Features
  • Other

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 139 results

  1. I'm looking to create a workflow that toggles my computer between these two settings (screencasting on laptop screen). Setting A 1. Display of time turned off 2. Menu bar on laptop screen Setting B 1. Display of time turned on 2. Menu bar on cinema screen Any advice?
  2. Most of the workflows I installed is from this Github repo. https://github.com/zenorocha/alfred-workflows However, I did find those workflows are being updated very frequently, so manual update is somehow tedious. It would be better if Alfred can implement a way to check whether remote alfredworkfllow files have been updated or not, and autoupdate them if necessary. Even better, implementing a Alfred workflows package manager would help both autoupdate and discover new packages.
  3. Is it possible to programatically create workflows? I'd like to generate a custom bash script for each user as a part of an alfred workflow. Preferably in ruby.
  4. I am trying to use a custom binary in a Script Filter. So far, there is only one issue: When I activate the script filter, the binary is called. If I close Alfred before the binary process terminates, that process begins to steal all of my RAM, as if in an infinite loop. Normally, it runs around 500KB of RAM for a split second; when improperly terminated, it will take up to 2GB until I quit the process with Activity Monitor. My script filter contains this code: ./binary "#{query}" How can I prevent the process from going haywire every time Alfred closes before the execution completes? (I do have access to the source code, if needed.)
  5. [updated] 390+ workflows added. I love Alfred 2 Wordflow very much, so I made this new collection site to download and share workflow from everybody. many workflows have been added, also you can submit yours or others workflows, just keep their Author Name and Released Page please. Website: http://www.alfredworkflow.com/ Submit you Works: http://www.alfredworkflow.com/submit-alfred-workflow/ ps: This is an un-offical site and all the workflows can be added to the site even if it is a small action. Enjoy~
  6. Hi great developers, you really need to sea this http://www.so.com/ctrl.ctrl.html . I've no doubt that this software is identical to alfred, and I believe that alfred could do more things more creatively. I've developed two small workflows, one of them is a qrcode generator, which outputs a picture. For now I've to save it down from remote server, and open it with Mac OSX native program Preview. But I think it would be much better if the picture was shown directly below the inputs area. Although there's an icon zone at the front of each result, it's really not enough. More layouts are really needed. You can check out that url address and will see many different layouts. Further more, workflows could take alfred to an extensive new world. Along with the progress of workflows, more developers and users will dive into this world. So a workflow center might be a great idea. It might be a website, with some supervisions. People would feel easier to extend their alfred and thought alfred greater than ever, and developer could touch end user more easily. The software above mentioned is running on windows for now, it's a great opertunity for alfred. Looking forward to see a better, stronger alfred!
  7. I'm sure I'm overlooking something here but none of the Applescript-based Workflows run. Nothing happens. The Alfred window disappears and that's it. I'm running Alfred V2 with Powerpack on a MacBook Pro running OSX 10.8.4. I can copy the script into the Applescript editor and comment out the "on alfred_script(q)" and the "end alfred_script" and it runs. Here is a script from Aaron B. Hockley's Create OmniFocus Tasks Workflow as an example. on alfred_script(q) tell application "OmniFocus" set theDoc to default document set theTask to q -- comment out the whole tell quick entry block if you want tasks to go straight to inbox tell quick entry open set NewTask to make new inbox task with properties {name:theTask} activate end tell end tell end alfred_script What am I missing? Thanks.
  8. Is there a way to backup a large library of workflows at one time? I know I can share them one at a time. Am I being thick or does this feature not exist?
  9. 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 complex that would wind up being, since I know Alfred always starts from the top of the results list, but thought I'd throw it out there.
  10. Well, I understand visual minimalism, and I get common usage of hotkeys working their way into your brain and muscle memory, but I wonder, those workflows that we all use occaisionally - damn it! I forgot the keyword.... How about a preference to enable the workflow keywords as a desktop overlay on hitting the alfred launch? or even a change in the text color within the albert input field as workflow keyword string possibilities are entered??? as more workflows are made and modified, the onus upon the memory to remember multiple keywords per workflow is bound to get a bit heavy! thanks for the really original possibilities with alfred 2. love your work.
  11. I'm tired of opening AppZapper (or AppCleaner), then opening a new Finder window to /Applications just to delete apps. Too many steps! Thankfully Alfred makes it easy with a quick workflow. If you're an AppZapper user, here's the workflow you need: Download Open App in AppZapper.zip Keyword is "zap" then search for your app. A notification will fire off and AppZapper should open up with your app and all its related files. Then zap them off your Mac. If you're an AppCleaner user, then here's the workflow you need: Download Open App in AppCleaner.zip Keyword is "clean" then search for your app. A notification will fire off and AppCleaner should open up with your app and all its related files. Then clean their butts off your Mac. The only caveat is that this will only work for one app at a time in both AppZapper and AppCleaner. AppZapper will need to be cleared manually (or zapped, or quit) before bringing in a second app; AppCleaner will clear the current app and bring in the second. Happy cleaning.
  12. I'm making a workflow that toggles an application feature on or off via a gui applescript. However, I'd like to have the workflow send a notification to the user indicating whether the feature has been enabled or disabled. How would I go about implementing this?
  13. Hi guys, wouldn't it be useful if the user would directly get to the preferences of the workflow that currently is triggered (keyword is entered into Alfred) when opening them? When some workflow doesn't behave how I want it to, then I'll open the preferences, but I always have to search for it first – this repeated itself often enough that I think there should be a solution for it ;-) Cheers!
  14. Hatmaker for Alfred - Alfred V2 Workflow https://github.com/bpinto/hatmaker Install & update alfred workflows straight from Alfred. Currently only alfredworkflow.com workflows are supported. Download the workflow Download the workflow below and open in Alfred. Features Currently only supports installing and updating. The rest will be added soon. Install a workflow install [workflow name] List outdated workflows outdated Update a workflow outdated > Select the outdated workflow Open workflow homepage Hold option key when installing or listing outdated workflows. Credits Everyone at this community.
  15. This will allow you to flush your DNS. This uses multiple methods to hand more versions of OS X. And has a pause in the middle of about 5 seconds. It will push a notification when completed. Just type flush and you are in business. Not much to take credit for here, all ideas came from others. Idea and icon taken from David Ferguson's Flush DNS script for pre 2.x Alfred and my need for a 2.x version. Script updated to support Mac OS X 10.7 & 10.8 with info from: http://hints.macworld.com/comment.php?mode=view&cid=130223 Download the workflow here: http://bit.ly/FlushDNSAlfred2
  16. Workflows' JSON API (new) (Recommended) API on Github: https://raw.github.com/hzlzh/AlfredWorkflow.com/master/workflow-api.json API backup: http://www.alfredworkflow.com/workflows-api/ -- API info -- Download Link by Author = workflow-download-link (Important!) Backup download link on Github = https://raw.github.com/hzlzh/AlfredWorkflow.com/master/Downloads/Workflows/ + workflow-file Everyone can load all the workflows' download links by using this API, mybe @phyllisstein can add this in Alleyoop.
  17. Hi all, I've have some problems with determining the locals language in bash script in workflows in Alfred2. I'm on OSX 10.7.5 FR. My script : DATE=$(echo "{query}" | sed -e's/HAEC/CEST/g' -e's/HNEC/CET/g'); export LC_TIME="fr_FR.UTF-8"; date -jf "%d %B %Y %T %Z" "$DATE" "+%Y%m%d%H%M%S" I use it : Select a text date (i.e. : "18 décembre 2006 19:24:12 HNEC"), use my hotkey to launch Alfred2/Workflow/Bashscript Problem : Works • In Alfred2 when month has NO accented character (i.e. : "18 janvier 2006 19:24:12 HNEC") • In terminal as is with or without month with accented characters Does NOT work • In Alfred2 when month has accented character Note : I had to add 'export LC_TIME="fr_FR.UTF-8"' as I assume Alfred bash script works in EN. It didn't work with french dates even though my whole system is in french and it DOES work in terminal without the export command. Also, I had to "translate" HAEC and HNEC as date command doesn't understand this frenchified CEST and CET. Any ideas on how I can bypass this problem ? Is it a bug ? Thanks in advance ! Hubert
  18. Please see this newer thread for a more up-to-date list of libraries that support Alfred 3 and beyond. Since the introduction of Alfred 2, there have been several extremely useful utility classes and other helpers crop up that simplify a lot of the tedious, common tasks associated with creating workflows. These utilities are developed and maintained by community members, not by the Alfred team. All support requests for these utilities should be directed to the original author. If you have another utility class that needs to be included in this list, send me a message or email (david@alfredapp.com) with information about it (name, description, short list of features, link to post or download page) and I will make sure that it gets added to the list. Special thanks to all the developers for their hard work and for sharing their work with us. Python Alfred-Workflow (by deanishe) A state-of-the-art Python library for Workflow developers. Support for Alfred 2 and 3. The library is simple to install, has no external dependencies, is very well-documented and maintained, and boasts an eye-wateringly high feature-to-size ratio at just 140 KB. Main features Catches, logs and notifies users (and developers) of errors in Workflows. No more confusing, silent failure. Super-simple, yet powerful data caching (e.g. from a web service) and storage. Easy-to-use storage of Workflow settings. Keychain access for secure storage (and cross-machine syncing) of sensitive data, like passwords and API keys. Tunable and understandable Alfred-like fuzzy search (e.g. got matches Game of Thrones as well as Baby Got Back. Or not: that's up to you.) Now with solid support for multi-word queries. Extremely lightweight, but full-featured, HTTP library with Requests-like interface, but just 12 KB instead of > 2 MB. Convenient access to standard OS X icons, for high-quality, familiar icons without adding size to the library. Also available via proper English. Pre-configured, built-in logging to enable simpler Workflow debugging. Painlessly run (update) scripts in the background without blocking your workflow, so you can still show "old" results while fetching new ones. Supports Alfred's new (version 2.3) modifier-specific subtitles. Simple support for 3rd-party libraries your Workflow relies on. "Magic" arguments to make developing/debugging Workflows so much easier, especially when helping less technically-inclined users. With "magic" arguments, you and your Workflow's users can open the Workflow's log file in Console.app, its cache and data directories in Finder, and its root directory in Finder orTerminal from the comfort of Alfred's query box. You can also delete the cache/data/settings if something is corrupted. Your workflow can update itself via GitHub releases. Accent-folding, so you can search non-ASCII text (e.g. voilà will be matched by voila) Functions to support migrating settings/data from older versions of your workflow. Well supported and kept up-to-date with Alfred's features as they are added. Alfred 3-only features Workflow variables Advanced modifiers Alfred 3-only updates And as you can see from the above links, there is extensive documentation, including a two-part tutorial on building a Workflow from scratch. Examples Here are a few examples of how you can do some pretty cools stuff in just a few lines of code. A simple Workflow I made to search Packal in ~90 lines of code. A simple Workflow to search your recent Pinboard posts in ~50 lines of code. A polished, user-friendly, wicked-fast Workflow to search your recent Pinboard posts in ~200 lines of code. Remember, each of these Workflows also has—for free—full error-catching and -logging support, and the ability to open its log file (which contains all errors) via Alfred's query box. No need to ask users to grub around in ~/Library or flounder in Terminal here. This is not the Workflow library 2014 deserves, but it's the one it needs Alp (developed by phyllisstein) alp is a Python module for developing Alfred workflows that bridges the gaps between Python and OS X and Python and Alfred, making the process of creating a workflow quick and easy. As it's essentially a collection of shortcuts for common and repetitive tasks, developers will find that working with alp results in less and more efficient code and a generally more sane workflow development experience. A painstaking guide to its various features, bells, and whistles is available in the README at the Github repository. Features: Simplified generation of feedback XML. Shortcuts for bundle ID, storage paths, settings, and arbitrary plist and JSON files. OS X interaction features, including the sending of additional notifications, interaction with the Keychain, and interaction with Spotlight. Internet interaction features, including bundled modules for making and caching HTTP requests, parsing markup data, and sending e-mail. The ability to remove unneeded modules for a svelte workflow bundle. Alfred-Python (developed by JinnLynn) alfred-python is a full-featured python module that helps building Alfed workflow quick and easy. Features: Simple feedback XML generation Provides functions for storing or retrieving cache data Workflow configuration management Includes an easy way to download remote file Easily get bundle id, query arguments, etc. More code example can be found on my own workflows. PHP Workflows (developed by David Ferguson) Workflows is a PHP library for building Alfred 2 workflows using PHP. Installation is quick and easy. Just drop in the Workflows.php class file, import it into your code, and initialize it. Full documentation, with usage examples can be found on David's blog. Features: Simple XML generation Read/writing files as plain text, json, etc. Read/write plist values Find local files Provide access to commonly used paths (home, cache, current, data storage, etc) Easy HTTP/cURL requests Haskell AlfredLibraryInHaskell (developed by raguay.customct) This is a Haskell library for creating Alfred workflows. AppleScript qWorkflow (developed by ursanrazvan) qWorkflow is an AppleScript library for creating workflows with Alfred 2. This library provides an object-oriented approach for working with plist settings files, reading and writing data to files, generating Alfred feedback results, requesting remote data, parsing JSON data, and more. Features: object-oriented approach to write less & more readable code heavily documented with code samples internal workflow introspection (finding the bundle ID, cache & storage paths) generate Alfred-compatible XML feedback with ease saving & retrieving workflow-related settings (with support for default settings file) remote data requests, as well as JSON support sending notifications through the Notification Center various internal utilities that improve AppleScript (string and date manipulation, file system utilities) More info & example workflows created with this support library can be found on the project's github repo Go goAlfred (Developed by raguay.customct) This go library is used to create workflows for Alfred 2 easier in the go language from Google (http://golang.org/). It will automatically create your cache and data directories. It also creates the xml listing for the feedback system. Examples included. Installation and Usage You install the library with:go get github.com/raguay/goAlfred # (You might have to use sudo). Any program that you want to use the library, just place this line in it: import "github.com/raguay/goAlfred" Functions The accessible function calls are: goAlfred.BundleId() - This will get your Bundle Id for your workflow. goAlfred.Cache() - This function returns the location of your cache directory. goAlfred.Home() - This function returns the location of your home directory. goAlfred.Data() - This function returns the location of your workflow's data directory. goAlfred.Path() - This function returns the location of your workflow's directory. goAlfred.Error() - Returns the last error received. AddResult( uid string, arg string, title string, sub string, icon string, valid string, auto string, rtype string) - This function allows you to build up the xml string for returning to Alfred. AddResultSimilar(instring string, uid string, arg string, title string, sub string, icon string, valid string, auto string, rtype string) - This function allows you to build up the xml string for returning to Alfred only if the title is similar to the instring given. goAlfred.SetDefaultString(title string) - This function sets a different default message if no results have been added. goAlfred.GetXML() - This function returns the XML string that needs to be given to Alfred. Bash BashWorkflowHandler (developed by _mk_) Features: create feedback xml save/read preferences volatile and non-volatile get workflow's cache dir get workflow's data dir get workflow's bundle id Usage examples can be found in the README at the GitHub repo. Bash Workflow Framework (developed by djc) BASH workflow framework which makes it simple to create a workflow which allows you to display feedback within Alfred after selecting a result, getting around the issue that "Script Filters are the only way to pass feedback to Alfred." Built to create easy reference workflows, or any other kind of workflow which does not want to leave Alfred immediately on selection of a result. Features: - Two modes for two different kinds of data: static and dynamic. - Creation of a static workflow only requires modification of a CSV-like file. - Static mode handles searching on query for you. - Dynamic workflow can be created using a BASH library ARF+. - Both modes allow for result and field-specific icons, validities, arguments, and autocomplete attributes. Extensive documentation in the README, and examples are included with download. Two methods of installation can be found on the github page. Ruby Alfred2-Ruby-Template (developed by zhauwu) A template for Ruby-based Alfred 2 workflow development. Features: Use standard bundler to easily package, manage, and update ruby gems in the workflow. Friendly exception and debug output to the Mac OS X Console Automate rescue feedback items to Alfred when something goes wrong. Automate saving and loading cached feedback Alfredo (developed by Dennis Paagman) Alfredo is simple ruby gem that makes it easy to create workflows and items to it. You can get started with only 4 lines of code. Features: Generates valid Workflow XML Add items with one line of code Supports all Alfred 2 workflow features Swift AlfredSwiftLibrary (developed by raguay.customct) General Alleyoop (developed by phyllisstein) Alleyoop is a meta-workflow that implements a system for updating other workflows. Users can make use of its features by downloading the workflow module and entering the query oop, which searches for compatible workflows and checks for available updates. Developers can implement Alleyoop compatibility with two simple, human-readable JSON files, described in the original post: one stored on a remote server, one placed in the workflow's folder. Alfred Dependency Downloader Framework (developer by Shawn Rice) Do you want to have versioned libraries and utilities live side-by-side? Do you want to make your workflows smaller but keep or expand the functionality with helper apps? Do you want to make sure that everything works regardless of whether Gatekeeper is active on other users' computers? Then you might consider implementing the Alfred Bundler* dependency framework in your workflows. If you want to see a _very_ basic implementation, then download an example workflow from Packal and open it up to see the workflow's anatomy. The libraries / utilities mentioned below are just pre-defined assets that you can load with no additional work. You can actually use this framework for any asset** by including a small JSON file with your workflow. Take a look at the documentation page on Github or the original post for more information.
  19. 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 reveal the xml.scpt you will need to edit, open the gf Script Filter and click the Open workflow folder button at the bottom of the window. Basic Usage: Add each item you would like to be displayed in your workflow to the itemList by passing a record containing the required labels to the xmlItem handler. For an in-depth description of each attribute, I have included pieces of David’s tutorial in the script’s comments. on run argv -- coerce the argv list to text set query to argv as text -- create an empty list to hold the items set itemList to {} -- Feedback item 1 set end of itemList to xmlItem({uid:"My uid", arg:"My arg", title:"My Title"}) -- Wrap the elements of the list with a declaration and return the list to Alfred return giveFeedback(itemList) end run xmlItem Handler Required labels: {uid:"My uid", arg:"My arg", title:"My Title"} Optional labels: subtitle:"My Subtitle" valid:"no" autocomplete:"Autocompleted text" icon:"icon.png" icon:"public.plain-text", iconAttribute:"filetype" -- iconAttribute must be used with icon icon:"/Applications", iconAttribute:"fileicon" -- iconAttribute must be used with icon Advanced Usage: Characters < > & " need to be escaped properly for XML. To insert items that may contain these characters, pass the string to the clean handler along with a true/false value to remove leading and trailing whitespace. clean(" Title with leading whitesplace & < > \" characters, trimming true", true) Alfred uses the uid attribute to learn which results are selected the most and then uses this information to sort your feedback. If you would like to manually arrange the returned items, use the uuid handler to generate a unique uid. In Alfred’s next release (after 2.0.2), this issue will be resolved and the item UID attribute will be optional. uid:uuid() Along with the workflow, I have included a list of file types that may be used as values for the icon label when paired with iconAttribute:”filetype”. See http://imgur.com/a/0zXVX for the corresponding icons.
  20. I have an idea. Why you dont release a kind of App Store for Workflows and Themes. This a good way for sharing, updating and store Workflows and Themes in a single good looking secure place.
  21. I would like to request the addition of version numbers for Alfred Workflows. As developers expand the workflows, I think it would be nice for them to be able to set the version number so it's easier to see what version you have and what version a developer has released. If added to the Bundle ID / Created By / Website, I think that would be nice. If displayed in small darker grey print next to the workflow name, that would be nice and easy, out of the way, and of value to both users, developers and you (as you can see if they are using an out of date workflow, etc.) Thanks! I hope to see this soon!
  22. Hey Alfred team, I would love it if we could have folders for our workflows. Once you get a bunch of them (especially ones you don't need to change a lot) it really is a messy list of workflows that the addition of folders could fix. Thanks a lot. Seriously love this app.
  23. Hi, It would be a great feature to be able to mark a workflow to be ran at starting, stopping Alfred. That way, we can write workflows to close out something started in a workflow. For instance, if I shutdown before logging my time off, it leaves my Alfred Time Keeper workflow mess up the data files. The best solution would be to auto log timing off up on shutdown. Richard
  24. I've been using Better Touch Tool to assign gestures to actions. Is it possible to use trackpad gestures to initiate workflows? Is anyone doing this? Any recommendations on how to do this? Thanks! (Meant to post this in the other forum)
  25. Hey everyone I was looking around to fill my workflow list from a fresh start up and I found it very difficult to find a good list of useful workflows that I can browse and download what I wanted. Its pretty time consuming going through the forums and going through each thread to find anything. Do you guys have any suggestions on this? I honestly feel like creating a simple website that would have a list of a bunch of workflows and themes for people to browse through and download. Developers could submit their workflows and users could request workflows. etc etc. Thoughts?
×
×
  • Create New...