@idantr would you like to prepare a pull-request to add the description as part of the tooltip?

For VS Code extensions, you should use Extensions view, not Plugins.

I'm not sure that we should work on enhancing Plugins view or looking into removing it. It is not used in practice.

I'm not sure that we should work on enhancing Plugins view or looking into removing it. It is not used in practice.

I asked a similar question in the past (#7375), in my opinion it is confusing to have both plugins and the extensions view. My concern however is that those that do not explicitly depend on @theia/vsx-registry will not have a view (since nothing pulls vsx-registry), and/or they might not want access to a marketplace so in that case do they add their own view? Should we add the view to api-samples as a reference?

My concern however is that those that do not explicitly depend on @theia/vsx-registry will not have a view (since nothing pulls vsx-registry), and/or they might not want access to a marketplace so in that case do they add their own view? Should we add the view to api-samples as a reference?

I assume they are either have own view or don't want to have view at all. Leaking dev time view to end users not really good.

My concern however is that those that do not explicitly depend on @theia/vsx-registry will not have a view (since nothing pulls vsx-registry), and/or they might not want access to a marketplace so in that case do they add their own view? Should we add the view to api-samples as a reference?

I assume they are either have own view or don't want to have view at all. Leaking dev time view to end users not really good.

I'm not sure what you meant by 'dev time view', but my idea was to either:

• remove the view completely from sources
• remove it from the plugin-system, but add it to api-samples as an example (and since some devs use it for testing purposes)

I do not think that applications should have both views by default (when pulling vsx-registry) since they overlap and one of them (plugins) has a limited set of functionality. It also requires additional maintenance to support both (which is mainly your argument for updating the plugins-view).

@akosyakov you had some comments in the past when I removed the view:

• #7388 (comment)
• #7388 (comment)

@akosyakov @vince-fugnitto @idantr
Is solution for this issue agreed upon?

@danarad05 from the above discussion @akosyakov should decide if plugins view should be removed/displayed in a different way or not.

You should bring unclear questions to the dev meeting where it would be decided by the community: https://github.com/eclipse-theia/theia/wiki/Dev-Meetings