Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Plugin Registry] [airgap] Each plugin should display proper icon #14510

Closed
vitaliy-guliy opened this issue Sep 11, 2019 · 12 comments
Closed

[Plugin Registry] [airgap] Each plugin should display proper icon #14510

vitaliy-guliy opened this issue Sep 11, 2019 · 12 comments
Labels
area/plugin-registry area/plugins kind/enhancement A feature request - must adhere to the feature request template.
Milestone

Comments

@vitaliy-guliy
Copy link
Contributor

Is your enhancement related to a problem? Please describe.

On the plugin registry each plugin refers on the same default icon. When displaying them on the UI, it looks not pretty nice

Screenshot from 2019-09-10 15-57-47

Describe the solution you'd like

We can apply the proper icons for each plugin.
Most of the plugins are VS Code extensions. Most of them are opensource with repository on GitHub. Each extension has package.json contains icon field which refers on the image hosted on that repository. We can easily refers on that images.

In result we may have the following

Screenshot from 2019-09-10 15-37-55

Screenshot from 2019-09-10 15-38-24

@vitaliy-guliy vitaliy-guliy added the kind/enhancement A feature request - must adhere to the feature request template. label Sep 11, 2019
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Sep 11, 2019
@tolusha
Copy link
Contributor

tolusha commented Sep 11, 2019

What about licensing?

@vitaliy-guliy
Copy link
Contributor Author

Licensing of what?

@slemeur slemeur added status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Sep 12, 2019
@slemeur
Copy link
Contributor

slemeur commented Sep 12, 2019

@vitaliy-guliy : I guess question from @tolusha is more about are we authorized to pull the images this way. I guess that if we are pulling from the repository it is fine.

Another aspect is how this would work if you are behind a proxy and can't reach github? Would it not be better to have that in the meta.yaml and directly in the plugin registry?

@nickboldt
Copy link
Contributor

See also #15581 re: icons in devfiles

@nickboldt
Copy link
Contributor

Another aspect is how this would work if you are behind a proxy and can't reach github? Would it not be better to have that in the meta.yaml and directly in the plugin registry?

Yes, icons should be cacheable inside the registry, just like .vsix files.

@nickboldt nickboldt changed the title Each plugin should display proper icon [Plugin Registry] [airgap] Each plugin should display proper icon Jan 29, 2020
@nickboldt nickboldt added area/install Issues related to installation, including offline/air gap and initial setup area/plugin-registry area/plugins area/productization and removed status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering. labels Jan 29, 2020
@tolusha tolusha removed the area/install Issues related to installation, including offline/air gap and initial setup label Feb 17, 2020
@sunix
Copy link
Contributor

sunix commented Mar 29, 2020

hello @vitaliy-guliy do you have any plans to implement that ?

@sunix
Copy link
Contributor

sunix commented Mar 30, 2020

Hello, first step, let's have the icons in the plugin registry like we do for devfile registry https://github.com/eclipse/che-devfile-registry/tree/master/images.
We will figure out later about a way to get that from the package.json.

@sunix sunix added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Mar 30, 2020
@amisevsk
Copy link
Contributor

The blocker issue for this is in how these images are retrieved; unless we want to ensure relative links are supported everywhere a plugin icon might be displayed, #15091 needs to be resolved before we throw icons into the registry.

@vitaliy-guliy
Copy link
Contributor Author

@sunix why not to point on the image on plugin repository on GitHub?
Something like this
https://github.com/eclipse/che-plugin-registry/blob/master/v3/plugins/ms-kubernetes-tools/vscode-kubernetes-tools/1.0.9/meta.yaml#L9

For each plugin we specify its source repository, which almost always contains the plugin logo.

@skabashnyuk skabashnyuk removed the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Mar 31, 2020
@sunix
Copy link
Contributor

sunix commented Apr 6, 2020

@vitaliy-guliy ok what ever, as long as this is working :)

@ericwill ericwill modified the milestones: 7.17, 7.18 Aug 5, 2020
@ericwill ericwill mentioned this issue Aug 5, 2020
29 tasks
@ericwill
Copy link
Contributor

This was fixed in 7.18 but was never closed.

@vitaliy-guliy
Copy link
Contributor Author

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/plugin-registry area/plugins kind/enhancement A feature request - must adhere to the feature request template.
Projects
None yet
Development

No branches or pull requests

9 participants