JJJJ reacted to stuartcryan in BTConnect Workflow - Would anyone find this useful - Released for Feedback December 26 2017
This is a quick one I have thrown together for my own use, I am hoping for some feedback on if anyone else would find this useful. I.e. do I keep it to myself, or productionise it properly?
I put this together primarily to connect quickly and easily to my Apple Airpods and an Alfred Workflow seemed like a great way to do that. I then expanded this to do hotspots and extra headphones as well.
Shoutout goes to Ian Gloude for his code on https://medium.com/@igloude/using-applescript-and-btt-to-make-the-airpods-experience-a-little-bit-better-6e78b12d33bd that makes this work. Essentially all this workflow does is do the clicks in the UI for you. I have logged a RADAR to Apple's BugReporter to request proper programmatic access to such Bluetooth functions also (for good long-term measure).
You can grab the beta workflow from: https://web.tresorit.com/l#5nvV-nDObUj8ovGFXYHP5g
Load up workflow Open Workflow Environment Variables Modify Workflow Environment Variables with your Bluetooth Device Names. PLEASE NOTE - read the notes alongside regarding regular and artistic apostrophes. AirPods especially seem to have artistic apostrophes in their name so you need to make sure you get the right one. Should be good to go
btairpods - connect to your airpods (they must be out of their case) btheadphones - connect to another set of defined headphones btphone - connect to phone network bthotspot - connect to iDevice hotspot (note this forces a several second delay between clicking the WiFi menu and clicking the hotspot as it usually takes a second for the hotspot's to show) dcbthotspot - disconnect from iDevice hotspot
JJJJ reacted to wtellier in Search IMDB
Because the previously shared workflows for IMDB-integration didn't work anymore I made my own. This is my first publicly shared workflow and this is also my first python-script. Probably things could have been programmed better, but it works for now.
So its not really fancy, but I think its workable, as long as IMDB doesn't change the API. Hope this workflow is some use for you all.
JJJJ reacted to Safari in Adding AirDrop Support to Alfred
This workflow allows you to invoke AirDrop in Alfred by typing airdrop.
Compared to hackish solutions that require AppleScript such as this and this, this simply executes airdrop.app directly, giving you the same experience as what you'd get when you type airdrop in Spotlight, e.g. it won't create duplicates if you already have one or more AirDrop windows or tabs opened, and lauching AirDrop won't bring all Finder windows to the front.
I'm actually a bit curious about why Alfred couldn't find airdrop.app after I added /System/Library/CoreServices/Finder.app/Contents/Applications/ to search scope. Until that works in Alfred, this is probably the best solution.
Download the workflow at Packal!
JJJJ reacted to drgrib in New Bear Alfred Workflow
I've created a new Bear Alfred workflow here:
It is faster compared to the current Bear Alfred workflow because it is written in Go instead of Python and has optimized SQL queries. It also adds tag searching and autocompletion, link pasting, and clipboard content to note on creation. I do appreciate the author of the original Bear Alfred workflow because I started mine from his design.
JJJJ reacted to Acidham in Apple Reminders
Adds reminders to Apples Reminders Inbox
Syntax: rm <Title>;<due day>;<time>
due day and time are empty: due day will be set to today with 3 hours from now time is empty: Reminder will be set to date provided at given time accepted date format: <day>.<months> or <day>.<months>.<year> or tomorrow, next week or <weekday> weekday e.g. "Wednesday": Reminder will be set to the next weekday accepted time format: <hours> or <hours>:<minutes> rmhelp opens quick help in Large Type
JJJJ reacted to iman in DownMedia — Download media from popular sources
Thanks Vitor!! This is the very first Alfred Workflow I have downloaded and used, and it works great!!
I am very, very, very new to Alfred and all things having to do with running commands in terminal and workflows using Alfred, etc...
I feel like I have opened up a whole new world of fun stuff to learn and use with my computer (Mac) and have you to thank.
I remember in 4th grade when I first was taught basic Algebra (2 - x = 5) and I was blown away at this new way to solve a problem, and felt so excited about Math and this fun new way to think. Unfortunately I went a different way in my life then was good for me - and only now at 45 years old do I have the motivation to learn something new. After using these workflows and learning about commands in terminal, etc.. I feel just like that kid in 4th grade, with my mind open and am looking forward to this new journey.
Thank you so much!
JJJJ reacted to Vookimedlo in alfred-various-screenshots
Dear Alfred users,
Here is another screenshots workflow for Alfred. I created it while I has learnt how to write an Alfred workflow. Maybe you find it useful.
Github - released package: https://github.com/vookimedlo/alfred-various-screenshots/releases/latest
Alfred 3 workflow for taking various screenshots.
Currently supported storages are the following.
Local drive Clipboard Dropbox service with an ability to share a link to the uploaded screenshot. Transfer.sh service with an ability to share a link to the uploaded screenshot. 0x0.st service with an ability to share a link to the uploaded screenshot. File.io service with an ability to share a link to the uploaded screenshot. After uploaded image is downloaded, the file is completely deleted!!! Installation
Install alfred-various-screenshots workflow. All further updates are handled automatically. Usage
In Alfred, type ss, which stands for ScreenShot and initiates a submenu which offers three options.
Screenshot - Area Screenshot - Screen Screenshot - Window
By default, the screenshot is stored in a file located at your ~/Desktop directory. This could be overridden, either by pressing the ⌘ key, ⌥ key, ⌃ key, ⇧ key, or Fn key.
⌘ - instructs the workflow to put a screenshot to the clipboard. ⌥ - shares a screenshot via Dropbox and stores a sharing link to the clipboard. ⌃ - shares a screenshot via Transfer.sh and stores a sharing link to the clipboard. ⇧ - shares a screenshot via File.io and stores a sharing link to the clipboard. Fn - shares a screenshot via 0x0.st and stores a sharing link to the clipboard. Screenshot files will be named according to the following pattern screenshot_%Y-%m-%d_%H-%M-%S.png
Y Year in full form (e.g., 2006). m Numeric month, a number from 1 to 12. d Day, a number from 1 to 31. H Hour, a number from 0 to 23. M Minutes, a number from 0 to 59. S Seconds, a number from 0 to 59. Default local screenshot folder ~/Desktop can be changed by the workflow DefaultLocalScreenshotFolder variable.
There is no need to install a Dropbox software to your MacOS. The only requirement is to log into the web Dropbox account and create an access token for the workflow.
Such generated access token shall be placed to the workflow DropboxAccessToken variable.
JJJJ reacted to deanishe in TimeZones - a World Clock script filter [updated to v1.7]
Bloody hell. That was fast!
JJJJ reacted to Jarek in TimeZones - a World Clock script filter [updated to v1.7]
Thank you for troubleshooting and suggesting a fix. I've included it in the branch and released v2.13
It can be downloaded from https://github.com/jaroslawhartman/TimeZones-Alfred/releases
JJJJ reacted to deanishe in Is there a workflow can reveal a opened file in finder
Also, if anyone's considering building a "Reveal in Finder" workflow, I'd very strongly recommend using a model similar to my AppScripts or Safari Assistant workflows.
Provide a built-in and a user script directory, and put application-specific scripts in there. When the workflow's run, it should grab the name/bundle ID of the active application, look for a corresponding script in the script directories and run it if found.
The potential for requests to add support for apps is basically limitless, so you really want to make it easy for users to add support for apps themselves, and to answer any feature requests to support app XYZ with "Sure. Write the necessary script, submit a PR, and I'll add it to the next release."
Otherwise, you're going to be dealing with endless support requests, many of which will be impossible to implement.
JJJJ reacted to dfay in Is there a workflow can reveal a opened file in finder
At the end of this thread there’s an example of trying to target multiple PDF apps (Skim, Preview and Devonthink) with a single Applescript - it’s doable but requires a lot of testing and customizing - unfortunately Applescript grammar isn’t standard even for these most basic tasks.
JJJJ reacted to vitor in Is there a workflow can reveal a opened file in finder
Then the file type doesn’t matter. That’s what I’m saying: you can tell an application to reveal a document in the Finder, it doesn’t matter what it is. And since you’re telling the application, you can’t have a generic solution, you’d have to include specific grammar for specific apps.
JJJJ reacted to deanishe in Is there a workflow can reveal a opened file in finder
To be clear: the kind of file is irrelevant, it's the application that the file is open in that matters.
JJJJ reacted to vitor in QuitArena — Quit all apps, with exceptions
Call qapps and all apps excluding the ones you set in the keep_alive Workflow Environment Variable will quit. The Finder is added to the exclusion list by default, unless you set kill_finder to true.
You’ll need to use the exact names of the apps as they present themselves to the system. To prevent multiple from quitting, separate their names with commas.
qprocesses will kill all processes, subject to the same keep_alive and kill_finder settings, meaning even things in the background that you don’t see will be asked to quit.
Note both options ask the apps to exit (SIGTERM) instead of telling them (SIGKILL). If you need to force processes to terminate, consider ProcessControl instead.
Download | Source
JJJJ reacted to bazerman in [Alfred 3] Google Inline Search (open URL + copy to clipboard)
I am still so gutted about this - anyone found any alternatives? As a non developer, what would be the learning curve like if I was to take this on myself and try to fix the HTML parsers?