Open in Client

[goyalyashpal]

Migrated 🍬 from https://github.com/open-vsx/publish-extensions/issues/484 ^f : VSCodium --> Client {sorry, dont know regex and its notations yet 😅😄}

Summary

Ability to open in a client, an extension's page directly from its link

Steps to try

1. To open an extension in client, whose id/link is available: example
2. Update: see this daiyam's comment
   ~~There's no option other than manually searching for that extension in the VSCodium. i dont know about other clients.~~

Details:

• There should be a button on open-vsx site to pass the intent to open extension in client
• The info about the intent is given at daiyam's comment

Old initial input

• It would be really nice if the open-vsx site has some mechanism to trigger "Open in Client" behaviour which will enable to directly open it in the client when extension is shared as id or link.
• For implementation, open-vsx will have to set a standard (link i guess 🤔), and
  all the clients which want to support this feature will enable the support for that standard in their applications.
  See for reference: multiple apps in the video (0:07) attached in "telegram" section below.
• similar to how intents work in android and different apps can support that intent
  like for a youtube music link: following apps support that: newpipe, youtube music, youtube, youtube go, most all browsers
• i GUESS this page Using-Open-VSX-in-VS-Code says smth on that matter, but since i havent tried it yet, asking: is it same as what this suggestion is about?

• The current requirement of manually searching:
  • requires mental effort
  • is time consuming
  • is VERRY inefficient
  • removes any chance for semi-automation

Rough mockup:

---

References:

• found in other sites, including for example: the ms-vsmarket site, or telegram site.

• Telegram: tg://resolve?domain=telegram

• MS-vsMarket: (ref: daiyam's comment) vscode:extension/darkriszty.markdown-table-prettify

[daiyam]

The url used to install the example extension on Visual Studio Marketplace is : vscode:extension/darkriszty.markdown-table-prettify. (vscode: is scheme associated with Visual Studio Code app)

While OpenVSX would need to support several editors, I'm thinking, the best solution would be to add a select input in footer so the user can select his/her preferred editor. And then, build the urls for that editor.

If it's VSCodium, then url would be vscodium:extension/darkriszty.markdown-table-prettify. If it's XYZ, then url would be xyz:extension/darkriszty.markdown-table-prettify.

[goyalyashpal]

vscode:extension/darkriszty.markdown-table-prettify vscodium:extension/...

thanks a lot for sharing the url syntax for extensions. but i dont think that site should encourage/support/try to cover the whole breadth of fragmentation as per the following comment by @akosyakov

... Although I am not sure where we should stop then, VSCodium is not a single consumer of Open VSX, neither primary. Why should it be special? Should we allow any fork of VS Code, i.e. Gitpod, openvscode-server, code-sever, any Theia based product?

[goyalyashpal]

oops, ignore my prev comment, had missed some point of the preceding comment.

[amvanbaren]

to add a select input in footer so the user can select his/her preferred editor. And then, build the urls for that editor.

I think it's better to add the editor select to the open button, because this is the only editor specific functionality on the site. Something like this:

We can add a user setting or use a cookie to store the user's preferred editor.