Community
Participate
Working Groups
I'd like to chose a specific Browser Support object from the registry to create a browser and open URLs from my eclipse UI component. The browser is really a URL handler for a URL to execute some action in Eclipse. Currently there is only access from the workbench to the currently active browser support. I'd like my contributed browser support not to be active. I'd rather instead find my browser support by id and then call createBrowser(...) on it without touching the currently active browser support. Think I'd need id optional attribute of type string for the extension point. If it's supplied then browser support cannot be made active for example and can only be invoked when accessed via it's id (not sure how best to access to via it's id). This is just an example.
I think adding optional "id" attribute in schema and new APIs to access browser without changing the current behavior is a safe change that we can try for Photon. Maybe in your initial use-case, what you'd like wouldn't be so much of an "id" but more a "supportedProtocols" attribute (and assume empty would mean any protocol with lower priority, while "springboot" would register the browserSupport for "springboot" with higher priority) and then the method "createBrowser(URL)" would give higher priority to your springboot browser when it finds springboot:/ URLs. As this is a new field, it would also be backward compatible. @Alex: do you think you can create the patch?
Yes, I'll look into creating a patch for this :-)
