claui

I found the task interesting enough that I actually made that workflow.

Oh, hey! Welcome to the forums (second post, but still)! In case you’re not recognising me from the picture/username, I didn’t restrain myself to that single trope.

As a small note, Packal is pretty much abandoned (the creators haven’t had much time to spend on it for a long while) and mostly in maintenance mode. Many things are broken, like search (I always get a database error). Using it as a central repository might not be the best bet, as of now.

I’ve been thinking for many months now how we could have a Homebrew-Cask-like system for Alfred Workflows. I never think of Homebrew-Cask itself because in my view Workflows need to have a GUI install to show the important README. However, if you’re interested in kicking some ideas around, I’m up for it. I think most (maybe even all) Homebrew-Cask maintainers are Alfred users.

I’d mostly care for an approach that would not rely on a centralised system for getting Workflow information, lest it die as well. I’ve made OneUpdater which is a self-contained Workflow-agnostic way to check for Workflow updates. It does not matter how you build the workflow, you can just plug it in, configure it once, and then forget it. If you ever want to get rid of it for some reason, you delete a single node and it’s done. Those are the “why”s of it: easy setup, no impositions on your code, no maintenance, easy to get rid of.

For an Alfred CLI installer, I’d like to keep those values. Have something that would continue to work even if the maintainers abandoned it.

Anyway, welcome again, nice to see you here. Just wanted to offer support to discuss ideas if you ever think about implementing your own system.

Have a nice day!

Update to fix a couple of bugs and update the icons. Grab v2 from GitHub or enter pwconf in Alfred and action the update item.

Try two things and let me know the outcome please.
 
1. Pop up Alfred and type Reload and press enter to reload the Application Cache.
2. If the above doesn't work, even though Spotlight finds them, try reindexing.
 
Let me know if this clears up your issue.

For me, it only seems to work when I give Calendar a bit of time to get ready, e. g. when I insert a delay like this:
 
set the clipboard to "{query}" as text tell application "Calendar" to activate delay 0.5 tell application "System Events" keystroke "n" using {command down} keystroke "v" using {command down} keystroke return end tell

Thank you ManicDee. Works great. But, at least for me, was not working if the Calendar app was not opened. Duplicating the "activate" line solves the problem. Full code I am using is:
tell application "Calendar" to activate set the clipboard to "{query}" as text tell application "Calendar" to activate tell application "System Events" keystroke "n" using {command down} keystroke "v" using {command down} keystroke return end tell Thanks again!

To allow Unicode characters:
set the clipboard to "{query}" as text tell application "Calendar" to activate tell application "System Events" keystroke "n" using {command down} keystroke "v" using {command down} keystroke return end tell Note that we're side-stepping the text entry by simply pasting the Unicode string into the field that is already selected.

This workflow allows you to enter a new event via Alfred using Calendar's quick entry box syntax. Type whatever you would enter in the quick entry box in Calendar in Alfred after the newevent keyword and hit enter. The workflow will pass what you type to Calendar through the Quick entry box allowing Calendar to automatically create the event.
 
Click here to download the workflow.