jopemachine Posted November 3, 2021 Share Posted November 3, 2021 I made a simple workflow using Squoosh. I hope this helps to someone Any feedbacks are welcomed. https://github.com/jopemachine/alfred-squoosh Link to comment
deanishe Posted November 3, 2021 Share Posted November 3, 2021 (edited) 6 hours ago, jopemachine said: Any feedbacks are welcomed. Probably worth mentioning that it's built as a Node package, not a workflow. A lot of people avoid such workflows because of all the issues the non-standard installation method causes. Edited November 3, 2021 by deanishe jopemachine 1 Link to comment
jopemachine Posted November 4, 2021 Author Share Posted November 4, 2021 15 hours ago, deanishe said: Probably worth mentioning that it's built as a Node package, not a workflow. A lot of people avoid such workflows because of all the issues the non-standard installation method causes. Thanks for your advice. I will try to build workflow with other language like Go next time if possible. Link to comment
deanishe Posted November 4, 2021 Share Posted November 4, 2021 3 hours ago, jopemachine said: I will try to build workflow with other language like Go next time if possible There's nothing wrong with writing workflows with Node. It's distributing them as NPM packages instead of as .alfredworkflow files that is problematic. Workflows installed via NPM/Alfy don't sync between machines because they're not actually installed in Alfred's workflow directory. When Alfred upgrades a workflow, it preserves user settings (variables, keywords, hotkeys), but Alfy deletes them because it blindly overwrites everything. I guess it's easier for developers, but it just kinda sucks for users. Link to comment
jopemachine Posted November 6, 2021 Author Share Posted November 6, 2021 On 11/5/2021 at 1:24 AM, deanishe said: There's nothing wrong with writing workflows with Node. It's distributing them as NPM packages instead of as .alfredworkflow files that is problematic. Workflows installed via NPM/Alfy don't sync between machines because they're not actually installed in Alfred's workflow directory. When Alfred upgrades a workflow, it preserves user settings (variables, keywords, hotkeys), but Alfy deletes them because it blindly overwrites everything. I guess it's easier for developers, but it just kinda sucks for users. Will the overwriting issue still remain even if I compress the alfy workflow into alfredworkflow? Link to comment
deanishe Posted November 6, 2021 Share Posted November 6, 2021 8 hours ago, jopemachine said: Will the overwriting issue still remain even if I compress the alfy workflow into alfredworkflow? No. The important thing is to ask Alfred to install the workflow itself, and let it worry about all of that. The simplest and best way to distribute workflows is as .alfredworkflow files. Then all you have to worry about is identifying a newer version and downloading it. Alfred takes care of the rest. Anything else is a bit silly. Updating is difficult to do properly, sucks if you don't do it properly, and it's important to keep your update code as simple as possible because your primary bugfix mechanism is a really bad place to have bugs. jopemachine 1 Link to comment
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