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

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. 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
  2. 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.
  3. 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.
  4. 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
  5. 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.
  6. 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.
  7. 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
  8. How do I set up a workflow to choose a specific contact in Contacts and send that person a message via the Messages app? (Akin to how Alfred allows a user to email a specific contact.) I started a new workflow that launches the Messages app, and I tried to add a Contact Action, but that doesn't exactly work: Contact Action comes before, rather than after, Messages -- and I want Messages to start first and enable a specific contact to be used as the input. I welcome advice and suggestions. Thanks!
  9. 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.
  10. 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)
  11. Proposed Feature: Provide a default argument that will be used in place of a query in the event that no query is provided. Rationale: In my particular use case, I have workflows that are mapped to urls, with the keywords representing unique customer identifiers within local/qa/production environments. For example: app.ourdomain.com/feature/{query}/some/path I'd like to have a single workflow that would populate the customerID field with a default value if no query is provided (the ID i'm working w/ 90% of the time), but that would still respect queries when they are used. Possible Implementation: Possibly something like: app.ourdomain.com/feature/{query|1234}/some/path
  12. I had this alfred.preferences file appear somewhere in my file system. I moved it to another directory and now my workflows in Alfred are missing. I don't want to spend time recreating my workflows. How do I quickly fix this if I can?
  13. 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?
  14. Recommendations for Sharing Workflows The forums have really been running well and you guys (and gals) have been creating some amazing workflows so far. I wanted to throw out a few suggestions though to make sure things stay organized, are easy to read, and easy to find. This will be an evolving document. Check back for questions regarding questions on posting your workflows. If you have a question that isn't answered within the contents of this thread, feel free to contact any of the moderators (Myself, Andrew, or Vero). Post Titles Be specific. Don't be overly descriptive about every little feature the workflow provides. Titles are best kept to the workflow name, and potentially a few words on the overall gist of what it does. Tags Be sure to set topic tags for your workflow post. This will make it easier for users searching on the forums to find your post/workflow easily based off of a few key words. Dependencies Please include a listing of all dependencies for your workflow. This will hopefully alleviate potential problems that users run into from attempting to run an installed workflow without an installed package being present. Examples of this would be Ruby gems or Python modules or even Python versions that are required for using the workflow. If a specific application is required for your workflow to function, be sure to include a link to that applications website, or a link to it in the App Store as well. Also include, if necessary, required versions of OS X. System Modifications If your workflow creates or modifies any supporting files that would alter the users environment, this should be noted. This will make it known up front that your workflow modifies system file X to achieve its functionality. Also, if the user uninstalls the workflow, how to remove these files or restore the originals. Screenshots They aren't required, but providing a screenshot or two for your workflow helps provide users with a good idea of what it is they are about to download. Descriptions help, but many users are wanting to pop in, get a quick visual, and download. Posting When sharing a new workflow, please be sure to create your own thread for it. By posting it in another workflows thread, your workflow may never reach the masses. Create your own thread so that it stands out and everyone will be able to find it easily. This helps remove confusion on which workflow to download if there are multiple workflows, or modified workflows posted within the same thread. It also helps ensure that the develop that spent their time and put in the hard work to create the workflow get credit for their work. Posting a patch/update/fix/modified version of a workflow in another authors thread may steal attention from their original work. So let's try to be considerate. Sharing Multiple Workflows Try to limit a new thread to a single workflow. The reason for this follows the situation mentioned above. Unless you have an abnormally long title, users casually browsing the forums may not realize how many workflows are available in the post, or what they are. Creating a separate post for workflows also creates an individual area for you to provide support or answer questions for that workflow alone. Modifying Existing Workflows Most developers are very open to feature requests for their published workflows. So before modifying someone else's workflows, check with the developer and see if they would add the feature first. If the requested feature is something that the developer doesn't plan on adding, of course you could add the feature yourself. If you think it's a feature that others would also find greatly useful and you decide that you would like to share your modified version, please be respectful of the original developer give them a heads up before hand. Also, be courteous and give credit to the original author and/or a link back to their original thread so that they receive some credit for their work. Nobody enjoys having their work stolen. Updating You Workflows When sharing an update to an already posted workflow, rather than creating another post in the existing thread, update the initial post to include desired information and updated download links (if necessary). This makes it easier for users to find the most up to date version of your workflows, along with information what is included in the update. You could also modify the thread title to indicate the date that the workflow was last updated. Notice: I'm also going to try to monitor this thread and keep it clean. If you post suggestions for other things to be added to the document, if they are merged in, I will probably remove your original post. Questions will also be treated the same way. If answers are later added into the original post, I may remove the original question. This will hopefully keep it so that all documentation remains in the original post so someone doesn't potentially have to search through several pages of questions for find a simple answer.
  15. I installed a bunch of workflows on my MBA. They all work perfectly. I went to sync with my Mac Mini (using DropBox) and I'm having issues with some of the workflows. The two I noticed had problems were the Google Instant Search and the Pinboard bookmark search. The workflows show up, but they don't operate correctly. Has anyone else had this issue? Is there a limitation on some of the workflows where they have to be manually installed on each machine? I've restarted Alfred and run the clear cache process.
  16. [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~
  17. WakeOnLan v1.1 https://dl.dropbox.com/u/677787/alfredworkflows/WakeOnLan2.alfredworkflow Now includes the possibility to automount a share after the NAS has been woken up. If you do not need this feature use 1.0 Credits for the Mounting part @malt3 on App.net WakeOnLan v1.0 https://dl.dropbox.com/u/677787/alfredworkflows/WakeOnLan.alfredworkflow WakeOnLan Python Workflow v1.0 Credits @dirkessl on App.net for helping me find the right Python-Script Original Python Script from: http://pastebin.com/3Zd9MvE1 *** IMPORTANT *** Edit the very end of the script with the MAC address of the device(s) you want to wake up. You may use more than one device, simply add another line Example: wake_on_lan('XX:XX:XX:XX:XX:XX') wake_on_lan('XX:XX:XX:XX:XX:XX')
  18. Hi there, I would like to share some workflows I have built. Play iTunes: pl [name|artist|album] Add Calendar Event cal meeting at 15 on 21 in shopping @Personal alarm 0 min 2 days Please, see my page: http://code.google.com/p/tox-alfred-workflows/ I am going to publish more. Thank you. Tox
  19. Hi guys! It would be awesome add a new argument in triggers' hotkey. I miss be able to use hotkeys over files that I found in Alfred's search. For instance, Imagine I search 'ios' and Alfred shows me the file/folder I was looking for. Then I press CMD + D and one action is triggered over the selected file in Alfred. Yes, I know that I can do this using Alfred's actions but I guess it's more comfortable be able to use hotkeys sometimes, isn't it? I hope you can find this helpful.
  20. 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.
  21. When using a Terminal Action in a workflow, the Terminal app is started and the command run successfully. If, however, a new tab is started with cmd-T or through the Terminal "Shell" menu, the command that Alfred originally sent to Terminal is run again in the new tab. Cheers, -Ben
  22. This tutorial is aimed at Alfred 2. Alfred 3 allows you to connect one Script Filter to another, so these workarounds are not necessary. (They might still be interesting, however.) [added 2017-03-20 by deanishe] Provided below is a workflow that provides a demonstration of how to reuse a single script filter or, how to chain multiple script filters together so that you can create the illusion of having multiple steps or allow you to further refine results from the first script filter, using the second. Demo 1 This demo shows how you can use AppleScript to call the next step (another script filter) after the first script filter has completed. This could be used to send the value of the first script filter into the second, or, you could just save the values to file and then read them all back in when you are done. This example will save the value to file. Demo 2 This demo shows how you can reuse a single script filter using autocompletion to separate multiple inputs with a delimiter. When the filter completes, you could then use that delimiter to split the string into its multiple parts. This works really well if your input data is numeric or short strings. Demo 3 This demo shows how you can reuse a single script filter, with AppleScript to provide multiple inputs/steps to the end user.The data entered by the user is saved to file in each step, then read in and appended together at the end. You could separate the final output with a delimiter and pass it on to something else if you wanted. There are many ways that this could be customized to your liking. Change the delimiters, how values are passed, etc. This thread is merely meant to provide examples of how this could be accomplished for those interested. Download the demo workflow here.
  23. 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!
  24. Hey all Alfred lovers out there, After David Ferguson created the PHP Workflows class to help PHP gurus create complex workflows with ease, I decided to create an equivalent solution for AppleScript gurus, because let's face it: you can't really do with PHP (or other languages) what you can do with AppleScript in terms of controlling your Mac system and its apps. This library provides an object-oriented library of functions for working with plist settings files, reading and writing data to files, generating Alfred feedback results, requesting remote data, and more. But before you begin working with it, please make sure you read the documentation first as it contains vital information on how to use it, as well as help & examples (there's even an example AlfredWorkflow file that uses this library to show you how you can use it for your own workflows). P.S. at the moment the library lacks JSON support since AppleScript doesn't know anything about it, so until I develop a JSON parser for AppleScript you can either use David's PHP class or improvise on my work and keep an eye on the github repository because I will probably add more AlfredWorkflows, and hopefully I'll manage to make a proper JSON parser in the meantime.
  25. I've some doubts how it works the sync when you make changes to a workflow, the only way I could sync the changes made was to export it after editing directly in Alfred preferences, and then reimport to make the tweaked version sync. Is there any way around? It would be nice to have a "reload workflow" option, that way we could edit the scripts from the sync folder and see it happen. Thank you
×
×
  • Create New...