Alexander Willner Posted January 5 Share Posted January 5 (edited) The workflow is already at https://alfred.app/workflows/alexanderwillner/optimize-images/ . However, it states "This workflow requires ImageOptim" which is not 100% correct. The workflow searches for various image optimisers in the path: "Please note that ImageOptim or related tools should be installed (e.g. via brew).". The tool "ImageOptim" just happens to automatically install most of them. Edited January 5 by Alexander Willner Sridhar Katakam 1 Link to comment Share on other sites More sharing options...
vitor Posted January 5 Share Posted January 5 11 hours ago, Alexander Willner said: it states "This workflow requires ImageOptim" which is not 100% correct. Indeed. However, one of two things is required: the app, or all the relevant Homebrew packages. Given the workflow’s name and icon, listing the app seems clearer and easier for users. Wouldn’t you prefer to support that set up (i.e. when getting bug reports) than the alternative? If not and you consider the Homebrew packages to be the desired method, let me know and so I can make the switch. For dependencies, I see:gifsiclesvgcleaneradvpngjpegoptimjpegtranoxipngpngcrushpngoutpngquantzopflipngDid I miss any? Link to comment Share on other sites More sharing options...
vitor Posted January 19 Share Posted January 19 @Alexander Willner I’m moving this to Completed, but the above stands if you want the change. You’ll still be able to reply to this post. Link to comment Share on other sites More sharing options...
Alexander Willner Posted January 21 Author Share Posted January 21 I see. What about: "This workflow requires either ImageOptim or any these image optimisers installed (e.g., via brew): gifsicle, svgcleaner, advpng, jpegoptim, jpegtran, oxipng, pngcrush, pngout, pngquant, zopflipng."? Link to comment Share on other sites More sharing options...
vitor Posted January 23 Share Posted January 23 The message is standardised, it’s either one dependency method or the other. Listing both as alternatives would add to the possible confusion, especially when the non-app route requires so many tools. Remember that the Gallery serves a large number of users with different skill levels; with every choice you add in installation methods you lose someone who’ll never take the time to understand the difference. I thought about this extensively when first adding this workflow in particular and picked the method which most will be able to more easily follow. Gallery pages link to the projects homepages where further nuances can be made, but the first impression should be as clear as possible and we should avoid a complicated decision even before a user can decide if the tool they’re looking at fits their needs. But again, either method can be listed. Link to comment Share on other sites More sharing options...
Alexander Willner Posted January 23 Author Share Posted January 23 Then let's keep it as it is. Thanks. vitor 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now