lsp-plugins icon indicating copy to clipboard operation
lsp-plugins copied to clipboard

Single launcher

Open stormbeforesunsetbee opened this issue 3 years ago • 8 comments

Hi! Is it possible to make the launchers one? I mean, this is annoying tho Screenshot from 2021-05-10 10-08-39 Sorry about that

stormbeforesunsetbee avatar May 10 '21 03:05 stormbeforesunsetbee

Hello!

You're not the only who claims about LSP icons flooding GNOME menu entries. The main problem is that GNOME is not following the XDG standard and not grouping these icons into a single folder.

Since 1.1.30 I decided to delegate the icon installation and maintenance to distribution maintainers by moving icon installation to a dedicated target in the makefile which is not run by default.

Please also see the #193 ticket for the detailed description.

If you have any questions/suggestions, please welcome.

sadko4u avatar May 10 '21 07:05 sadko4u

Hmm, yeah, but I think not providing launchers at all is way too extreme. What about making a single app launcher like "Chrome App Launcher" but it's a window, not a popup. You can imagine it as "GNOME Tweaks" or something

stormbeforesunsetbee avatar May 11 '21 06:05 stormbeforesunsetbee

I agree with @sadko4u , dealing with Gnome is kinda pain in the ass. It is the only environment not providing grouping of desktop files (while there are even special desktop directory annotations for them).

I know it's not the fault of users, they are the victims, but I think that it should be more on the Gnome platform to get the request and implement back directory views in their shell. That makes a lot of work to make a simple window launcher integrated to the environment, and that's also something that would be necessary for other projects.

P.S.: it's easy for me to say that because I am not a Gnome user lol... but I understand both your need and the project's maintainer issue to implement it.

riri avatar May 11 '21 06:05 riri

By another side, implementing launcher application is a good option but for 1.1.x it is not reasonable. I think it will be good to implement 1.2.0 (with complete redesign of core modules) release first and then add a launcher application. So I would consider this issue to be implemented not earlier than 1.2.0 release.

sadko4u avatar May 11 '21 06:05 sadko4u

with complete redesign of core modules

Dang! Can't believe that a simple app launcher affects the whole core modules :D lol PS: I never contributed here tho, so I don't know what's going on with the source code

but I understand both your need and the project's maintainer issue to implement it.

It's gonna be a pain for multi-desktop-manager distro maintainers if we change our design :v

stormbeforesunsetbee avatar May 11 '21 07:05 stormbeforesunsetbee

@rivanfebrian123 I think you understood me a bit improperly. The launcher won't affect core modules. But the introduction of the launcher is not reasonable at this time since the core of LSP Plugins project is varying significantly when introducing 1.2.0.

My point was that we can wait a bit until 1.2.0 is released and then introduce the launcher application for standalone version of plugins.

sadko4u avatar May 11 '21 12:05 sadko4u

Oh... I see. Also, I think we should make a guideline about packaging this library. For example:

"You can provide two different packages for LSP, for example: lsp-plugin-gnome (or lsp-plugin-single-launcher) and lsp-plugin (the 'default' one, with multiple launchers)"

stormbeforesunsetbee avatar May 11 '21 14:05 stormbeforesunsetbee

The implementation of single launcher was moved to further releases.

sadko4u avatar Mar 25 '22 23:03 sadko4u