GithubHelp home page GithubHelp logo

Show addons about linux-store-frontend HOT 12 OPEN

flathub-infra avatar flathub-infra commented on July 30, 2024 3
Show addons

from linux-store-frontend.

Comments (12)

jgarciao avatar jgarciao commented on July 30, 2024 1

I guess I can obtain this information from this entry in the appdata:

<component type="addon">
	<id>io.github.Hexchat.Plugin.Perl</id>
	<name>Perl Scripting</name>
	<summary>Scripting interface for Perl</summary>
	<project_license>GPL-3.0+</project_license>
	<url type="homepage">https://hexchat.github.io/</url>
	<extends>io.github.Hexchat.desktop</extends>
	<bundle type="flatpak" sdk="org.gnome.Sdk/x86_64/3.26">runtime/io.github.Hexchat.Plugin.Perl/x86_64/2</bundle>
</component>

from linux-store-frontend.

somas95 avatar somas95 commented on July 30, 2024

In the meantime another line could be added to the "command line instructions" section of the pages whose applications have extensions:
image

from linux-store-frontend.

allanday avatar allanday commented on July 30, 2024

It's worth remembering that Flathub doesn't know which add-ons a user has installed. A list of install buttons for application add-ons could be frustrating to use.

from linux-store-frontend.

somas95 avatar somas95 commented on July 30, 2024

Why it would need to know which add-ons are installed? It also doesn't know which apps are installed and the list of install buttons for applications isn't frustrating to use. Also, the number of add-ons any typical application has is pretty low, and in any case even listing them in a separate category outside the application pages they extend is better than don't listing them at all

from linux-store-frontend.

allanday avatar allanday commented on July 30, 2024

Why it would need to know which add-ons are installed?

It's easier to verify which apps you have installed, compared with add-ons.

the number of add-ons any typical application has is pretty low

Checking here, GIMP has 14, Blender has 2, gedit has 20, Nautilus has 4, Thunderbird has 3. On that basis, there's a fairly wide range in the number of add-ons.

even listing them in a separate category outside the application pages they extend is better than don't listing them at all

I don't think I suggested not listing them. Just pointing out that we need to be careful about introducing functionality that might turn out to be poorly supported.

from linux-store-frontend.

hfiguiere avatar hfiguiere commented on July 30, 2024

Now that there are more plugins, like Linux audio, this would be an awesome feature to have.

from linux-store-frontend.

hfiguiere avatar hfiguiere commented on July 30, 2024

For the numbers of Linux Audio, as of right now:

  • LV2 Plugins: 14
  • LADSPA: 3
  • VST: 3
  • VST3: 1

And the list is growing.

Applications that support any of these kinds: 10 at least.

from linux-store-frontend.

hfiguiere avatar hfiguiere commented on July 30, 2024

Checking here, GIMP has 14, Blender has 2, gedit has 20, Nautilus has 4, Thunderbird has 3. On that basis, there's a fairly wide range in the number of add-ons.

Not sure where you got the GIMP from, because the GIMP Plugins were just merged this morning for flathub availability.

There are currently 5 GIMP plugins.

from linux-store-frontend.

Jehan avatar Jehan commented on July 30, 2024

Extension also have appdata, which could potentially contain screenshots, nice descriptions and more. So it would be nice for these extensions to have their own page on flathub.

Then the page of the parent application would only contain a list of the extensions with name and short description (<summary> tag contents) and a link to go to the specific extension page (with more detailed description, changelog, screenshots, website links, etc. Just like a standalone application basically).

And the "Install" button will be on each individual extension page. After thinking a bit, I'm not sure that we should encourage any "install all at once without thinking" behavior. Plug-ins are still real applications, made by third party. This should be clear to people and I think that encouraging reading about an application (any, even as plug-in of another), its license, and maybe looking up its website and such is the better way. Encourage informed choices in other words.

Then people are welcome to just do speed clicks if they don't care at all, but at least the platform gives them a choice. A list with only name/summary where you can directly install on the main application page (like in GNOME Software) makes it look like the extensions are made by the same developers and don't allow informed choices.

from linux-store-frontend.

hfiguiere avatar hfiguiere commented on July 30, 2024

This shouldn't be based exclusively on the appstream data. While it is valid for GIMP plugins, in the case of Linux Audio plugins, it is important to use the extension point listed in the package metadata as the appstream only list the base app which is just an empty app.

from linux-store-frontend.

jakobjakobson13 avatar jakobjakobson13 commented on July 30, 2024

Hi. I just wondered if there was any progress on this issue?

The reason for my curiousity is the following: I recently filed a bug against firefox because I was not aware that the ffmpeg was a optional dependency of firefox.
If I would have known that or if flathub.com or Gnome software had shown me that ffmpeg is an optional extension of firefox that does not get installed by default, I would have installed it manually and had not filed the bug report.

So is there any way to show the extensions of a package on flathub.com? Or to install such optional depencies by default? I did not find the suitable command.

Edit: After some more research I think that is probably also related to the firefox manifest. But the extension of Gnome games is nonetheless not listed on flathub.org.

from linux-store-frontend.

razzeee avatar razzeee commented on July 30, 2024

For reference
flathub-infra/backend#86
flathub-infra/frontend#128

from linux-store-frontend.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.