Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


shmulvad last won the day on June 11 2020

shmulvad had the most liked content!

Recent Profile Visitors

591 profile views

shmulvad's Achievements


Member (4/5)



  1. @PHlllPP You can change the renaming logic in the file tiny_upload.py in the function get_new_and_bak_file() to suit your needs. But your changes will be overwritten when the workflow is updated next time so it is not recommended.
  2. @PHlllPP You need to edit the workflow variables. Click the button that looks like [x]. As for your other question, I don’t really see that the benefit in allowing multiple ways of handling renaming originals would outweight the additional mental burden. I would need some convincing arguments to do this.
  3. @Geoffrey I've released version 1.0.2 where the issue regarding bundling of the requests library is fixed and now you can also set a workflow variable KEEP_BACKUPS to either True or False (True per default) that determines whether or not to keep the .bak files.
  4. @dsrjarman, I've added a new option for toggling that accomplishes what you ask for in v1.1.1. Be aware that Alfred strips away the hotkeys from workflows you download, so after downloading it you'll need to set the hotkey (once).
  5. Thanks for making me aware of the unbundled library. Good to hear you got it solved for now, but as deanishe says the proper solution is for it to be bundled. I am busy with exams at the moment but will try to release a new version where this is fixed soon. I will probably look into your other suggestion as well, but no promises on when.
  6. It is just the installation I use per default on my personal system if I do not set up a new separate environment for a Python project. I wrote the workflow because I personally had a use case for it and afterward thought I might as well release it publicly now that the workflow existed anyway. When I tried using just "python" from within Alfred to call it, it didn't work on my system (even though "python --version" gives me 3.8.5 in a regular terminal session, even when no conda env is activated). It could be fixed by using the absolute path, so I just did that. I can see it also works (on my system at least) when using "python3" which I agree would have been a better choice as the default.
  7. Hi Dan. Sorry, but I do not have a M1 machine to test on. I am not sure what causes the issue based on your information, but since at least some of the workflow works based on your information, I think it is not a problem with your Python version and something else is causing it. Can you check the log using the Workflow Debugger and report back on what you see?
  8. I've added the code to remove the quarantine flag as suggested by @vitor. However, before I did this, I didn't seem to get the warning myself when I deleted the binary and then added it as a new freshly downloaded one. So I'm not sure whether or not this fixes it.
  9. Nice to hear that you like it, DanP! I don't know how to not have that message show up. If someone more experienced in macOS development here on the forum can me tell how to accomplish it (without having to buy an Apple Developer account), I'll be happy to implement it.
  10. Sorry about that. This workflow uses Python 3. Does it work if you do "which python3" in your Terminal and set that as the path for the variable "pythonPath" in the workflow?
  11. An Alfred 4 workflow for quickly compressing and resizing images using TinyPNG. Simply select a collection of images or a folder in Finder and activate the workflow. Installation and Getting Started Install alfred-tinypng workflow. All further updates are handled automatically. You will need to configure the workflow with an API key from TinyPNG. Type tinypng_api to get a link to the pagewhere you can get your API key and to actually set the key when you have gotten it. Usage Select either a folder, image file or a number of image files in Finder. Afterward, open Alfred and type tinypng. You are presented with the following choices: Choose an item based on what you want. When selected, the workflow will start compressing/resizing the image(s). After it is done, they will be saved to the same directory and with the same filename as the original image. The original image will be preserved with .bak prepended before the file extension. I.e. if compressing img.jpg, this will now become img.bak.jpg and the compressed image will be saved as img.jpg. Refer to the TinyPNG documentation for a full explanation of the different resizing options. Why? Another TinyPNG workflow already exists It doesn't support choosing the files based on what is selected in Finder (which I personally prefer). Only simple compression is supported whereas all TinyPNG compressions and resizing options are supported in this workflow. It seems to be abandoned by the creator (has not been updated since 2015). Credits The workflow makes use of the following: OneUpdater by vitorgalvao for handling automatic updates. TinyPNG Python API Code and more can be viewed on the associated GitHub-repo. If you find this workflow useful, stars are appreciated.
  12. Thank you for the workflow, it is very useful! Just a note about automatic updates: When you're hosting the package on Github anyway there is a ready made solution that requires almost nothing of you, meaning you can easily add this feature to your workflow. Check out https://github.com/vitorgalvao/alfred-workflows/tree/master/OneUpdater
  13. I don't know if you're still active on this forum, but if so, I've just released a workflow that can quickly turn off/on Night Shift:
  14. NightShift Quickly turn on/off Night Shift or set it to a custom value between 0 - 100. Installation To download, visit the latest release at GitHub. All further updates are handled automatically. Description Quickly turn on/off Night Shift or set it to a value between 0-100. No more fiddling with deep settings when you either want to save your eyes or need to work with accurate colors! In Alfred, type night followed by either off, on or a number between 0 - 100. Credits The workflow makes use of the following: nshift by leberwurstsaft as the backend for setting the values. OneUpdater by vitorgalvao for handling automatic updates.
  15. Okay, I didn't know that - thanks for letting me know! The workflow is now updated to use JSON. I'll agree with you, that is much cleaner.
  • Create New...