Quick Commands api
Is there a possibility of porting the quick commands to an external program? Specifically, I'm interested in an Alfred workflow - which would smoothen the operation if you already use alfred a lot.
I realise a lot of the functions from the quick commands can be replicated by Alfred without any direct link, but it would perhaps be more complete if it could
I don't know how Alfred works, I'm using Quicksilver myself instead. And of course there is no plugin for Vivaldi on Quicksilver, because no user has written one. So if there are also user written plugins for Alfred, the possibility is there, but you gotta code it yourself. I imagine the number of people, who use both Alfred and Vivaldi and have the knowledge to do something about it, is incredibly small.
Thanks for the reply, I guess it would be known if such a person existed.
Maybe I'll dabble with it myself one day
Maybe ask directly in Vivaldi Discord, some real Devs hang in there. That if you don't mind to register at all.
@dleon Good tip, thanks
Really interesting question!
Did they said something about it on/in Discord?
At the moment we could create a workflow which would focus Vivaldi and simulate a shotcut-keypress sequence or with an apple-script accessing menu-entrys.
But it would be much more interesting if every command/item would be accessible via URL-Request:
And access to all bookmarks via XML could (already would?) be also possible!
That's what I do at the moment with BetterTouchTool, which gives me a global hotkey. But as you say it needs to focus vivaldi. Exactly what you wrote as url-requests would be perfect.
Discord didn't give me that much info, other than that it wasn't any except perhaps an internal one.
It's also build on Chromium, so a few modifications to a lot of the Chrome workflows is sufficient to make them work with Vivaldi.
It's then possible I think to bundle them all together (one for tabs, history, boomarks etc). But the commands will not be there ofc, like Pin/Unpin tab, split horizontally etc. Which isn't that much of a deal, since they are only relevant when Vivaldi is the active application.
Not to cut your hope but;
so a few modifications
Not if the modification could break Vivaldi own codes. Chromium upstream change a little bit their ways for Window Handling, that alone already make Vivaldi devs busy for days it seem.
Little one change on Chromium upstream could mean party in devs kitchen.
Maybe I was unclear, I meant in the Alfred Workflows designed to work with Chromium or Chrome browser