Thanks for the input anyway!
During development of cocoaDialog wrappers I overlooked adding automatic user permissions. I'll make sure to fix that in the next update
Well, the Packal updater is perfectly accurate because it will always update your workflows to the newest version on Packal, which is not necessarily the newest version.
I designed Packal in a way that only the workflow author could update their workflows in order to make all of the releases there as authoritative and official as possible. Since the update can come only from them, it's the workflow authors' responsibility to keep their workflow up to date on Packal. For me, it's also a question of letting the authors choose to distribute their work on Packal rather than choosing for them. They might not want to put the newest version on Packal for some reason or another. It may be that they want the most stable ones on there only. Or they may have come to dislike Packal and decided to stop using the repository.
That being said, I have some code on the backburner that will make it much easier for authors to submit and to keep their workflows up to date on Packal. It's basically a mixture of ways to use metadata from the workflow internals along with some supplement that will allow releases to be pushed via Github hooks as well as from Alfred itself. Hopefully those improvements will help keep versions updated on Packal.
Sure, you can edit the workflow to do this without much work on my end
Basically, you're going to find the connection between a Run Script object and a Growl output. When you find this connection, simply add another connection between that Run Script object and a Copy to Clipboard output.
On my end, the screenshot below does what I described above. If you don't want the Growl notification, simply delete the Growl object from the workflow
VadimV got a reaction from Tyler Eich in Wolfram|Alpha workflow
