This repository has been archived by the owner on May 3, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 23
Add ability to specify list of supported platforms for a plugin #115
Comments
A very good feature it will help avoid confusion. |
Thank you. You will be notified by transifex when there are new strings to translate. |
We should also change the wizard to ask the developer of the plugin what platforms are supported. |
Yes |
ColinDuquesnoy
added a commit
that referenced
this issue
Sep 17, 2017
ColinDuquesnoy
added a commit
that referenced
this issue
Sep 17, 2017
ColinDuquesnoy
added a commit
that referenced
this issue
Sep 17, 2017
ColinDuquesnoy
added a commit
that referenced
this issue
Sep 17, 2017
ColinDuquesnoy
added a commit
that referenced
this issue
Sep 17, 2017
ColinDuquesnoy
added a commit
that referenced
this issue
Sep 17, 2017
ColinDuquesnoy
added a commit
that referenced
this issue
Sep 17, 2017
ColinDuquesnoy
added a commit
that referenced
this issue
Sep 17, 2017
The German translation is ready. |
Merged
ColinDuquesnoy
added a commit
that referenced
this issue
Sep 23, 2017
See #115 (issuecomment-331536513)
@ZeroDot1 No it is a bug. I fixed it. Thank you! |
Merged
Closed
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Some plugin do not work on some specific platform (e.g. platform where there is no way to get proprietary codecs).
There would be a new field in the plugin metadata that is a list of supported platforms. The plugin manager would skip plugins if the current platform is not supported and the service wouldn't even show up in the services selection grid.
List of platforms:
Example of a plugin that works only on GNU/Linux but not from an AppImage:
And here is an example of plugin that works everywhere:
This
could evenshould replace therequire_proprietary_codecs
key.The text was updated successfully, but these errors were encountered: