Re: [platform-dev] How can usiSchemaHandlers be used in internal web bro

["Becker, Matthias" <ma.becker@xxxxxxx>]

Hi Rolf,

 

as far as I know you can only register once application in the operating system that handles a given URI schemes. And that is also handled in the link handlers pref page.

If we find out that a uri scheme is handles by another application (not the binary currently running) we don’t let the user activate the handler in this eclipse instance

because we would “steal” the uri scheme from another application. This other application may even be a none-eclipse based application and this app may not have

a setting similar to the “link handlers” pref page to re-enabled it’s handler there.

We could think about a “Activate Anyway” option in the link handler’s pref page if the user “really really” what’s to “steal” the link handler from another app.

 

But once again: Only one app hand handle an URI scheme (and that’s an OS limitation and not an eclipse limitation).

Regards,

Matthias

 

From: <platform-dev-bounces@xxxxxxxxxxx> on behalf of Rolf Theunissen <rolf.theunissen@xxxxxxxxx>
Reply to: "Eclipse platform general developers list." <platform-dev@xxxxxxxxxxx>
Date: Wednesday, 8. April 2020 at 08:28
To: "Eclipse platform general developers list." <platform-dev@xxxxxxxxxxx>
Subject: Re: [platform-dev] How can usiSchemaHandlers be used in internal web browser?

 

Hi Matthias,

 

I would also assume that if the link handler is correctly registered it would work also work for the internal browser. However, I really wonder what the interaction would be when using multiple instances of Eclipse. I heavily use Oomph and as a result I have dozens of Eclipse installations. How to ensure that the link is opened in a specific instance? How to ensure that is handled by the current instance?

 

Regards,

Rolf

 

Op wo 8 apr. 2020 om 08:17 schreef Becker, Matthias <ma.becker@xxxxxxx>:

Hi Mickael,

 

I think the idea of the eclipse+mpc uri scheme was to replace the drag&drop of an link from the marketplace to the eclipse window with a more intuitive way. So user’s would simply click a link on the marketplace website.

I don’t know why the marketplace website does not render these links at the moment.

The downside of this is (currently) that the user explicitly has to enable this link hander on the link handers pref page. We did not implement an automatic registration because this writes stuff into the OS and we think such

stuff should always be triggered by a user-interaction.

One could think about an enhancement that proactively asks the users if he wants to enable a new link handler. Oomph could do that when you install a new eclipse but we also need a way to enable this when oomph is not used.

We could fire up a dialog (delayed at the start of the IDE) that basically shows the table from the link handers pref page asking which handlers should be activated. But this would something new to the Eclipse IDE. I never have seen

such (very intrusive) dialogs in the Eclipse IDE.

 

Regarding the internal web browser. Isn’t that just an embedded browser. So I would assume that once the link handler is successfully registered in the OS that links in the internal browsers also works as in the external browser…

 

Regards,

Matthias

 

From: <platform-dev-bounces@xxxxxxxxxxx> on behalf of Mickael Istria <mistria@xxxxxxxxxx>
Reply to: "Eclipse platform general developers list." <platform-dev@xxxxxxxxxxx>
Date: Tuesday, 7. April 2020 at 18:12
To: "Eclipse platform general developers list." <platform-dev@xxxxxxxxxxx>
Subject: [platform-dev] How can usiSchemaHandlers be used in internal web browser?

 

Hi all,

 

I'm brainstorming about possibilities to improve and simplify Marketplace integration in Eclipse IDE, ideally by reducing the amount of specific UI it uses and leveraging more the website (so we maintain a single web UI to consume in the IDE instead of having another view to maintain it it as well).

I see MPC has enabled support for `eclipse+mpc` protocol handler, that's great as invoking some CLI like `eclipse eclipse+mpc://marketplace.eclipse.org/install/1640500` works fine.

However, I was expected that such `eclipse+mpc` links in the Internal Web Browser would trigger the protocol handler and thus show the Marketplace Client dialog but it was not the case.

So I'm curious about the cases where those protocol handlers are supposed to work out of the box? Is there some setting, or preference or some existing views where I can have a such links working on a single click?

If not, are there bugs open on this topic I could monitor/participate to?

 

Thanks in advance

--

Mickael Istria

Eclipse IDE developer, for Red Hat Developers

_______________________________________________
platform-dev mailing list
platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev