[6.2][#1548] Install plugins from remote repository

[miurahr]

Pull request type

Please check the type of change your PR introduces:

• Bug fix
• Feature
• Documentation
• Build and release changes
• Other (describe below)

Which ticket is resolved?

• Feature requests: https://sourceforge.net/p/omegat/feature-requests/1548/

• Title: Plugin download and install manager

• Preference->Plugin dialog show plugin information in 3-pain

  • https://sourceforge.net/p/omegat/feature-requests/1549/

• Plugin preference table order (external first)

  • https://sourceforge.net/p/omegat/feature-requests/1545/

What does this PR change?

• Change Preference->plugins UI to 2 pains, left side is a list of plugins, right side is a detail text box.
• Add plugin download thread
• Update PluginInformation to handle remote URL and SHA256
• Download remote database and construct plugin list as preference->plugin UI table.

Other information

Plugin database is created as https://github.com/omegat-org/omegat-plugins/

[brandelune]

Is there a reason why we don't have a milestone anymore?

[miurahr]

We need to have a discussion how to manage 3rd party plugin registry in core team or community, how to be a database format of 3rd party plugins, how to accept an addition/modification/removal request, how to decide accept or decline, how to remove an item from the list, etc....

[brandelune]

Sure, but we can have that feature included in the code, and then start the discussion based on the feature requirements, don't you think so?

Is that what is keeping you from "targeting" 6.1?

[miurahr]

Sure, but we can have that feature included in the code, and then start the discussion based on the feature requirements, don't you think so?

There is no consensus with you and core team to have an obligation of maintains certified plugin database on the web.
There is also no discussion how we should have a database data format and its work flows.

Once the code included, above is forced to you with the assumptions of the code.

OK, PLEASE maintain the database by @brandelune !? Is it what you want?

@amake said

This gets us into an entirely new area for the project (hosting a directory of plugins) so I want to take a thorough look before we commit to it.

[miurahr]

Because we publish Current OmegaT versions on OmegaT web,
https://omegat.sourceforge.io/Version-latest.properties, it may be possible to publish plugin list like https://omegat.sourceforge.io/plugins-latest.xml

[brandelune]

Ok, let's have this discussion on the list.

https://sourceforge.net/p/omegat/mailman/message/37746064/

[miurahr]

Now we have a JSON style database.

[miurahr]

Improve "preferences > plugins" UI and localize type and status column.

[miurahr]

OkAPI filters plugin for OmegaT 1.13-1.45.0 is released with support for new Plugin configuration UI.

It looks better for management.

[miurahr]

Are there any good way to check downloaded jar file is not malformed using signature file jar.asc?
In current proposed procedure ask plugin developer to register their GnuPG/OpenPGP public key in GitHub account.
Is it possible for OmegaT to detect signer account and download a public key?

[miurahr]

Now "description" field is not localized. There is no specification how to define localized description in MANIFEST.
Does anyone have idea how to realize it?

[Kazephil]

I think update is better than upgrade:

• PREFS_PLUGIN_UPDATE=Update

[Kazephil]

Following from the above:

• PLUGIN_STATUS_UPDATABLE=Update available

Updatable is better for the key name, but "update available" is more natural for users.

[Kazephil]

Now "description" field is not localized. There is no specification how to define localized description in MANIFEST. Does anyone have idea how to realize it?

That might be a good question for the development list. I unfortunately don't know much about MANIFEST files, so I can't make any relevant suggestions.

[Kazephil]

A more general comment: this looks much better than the current plugin UI.

One question, though. How is the initial order of the plugins shown determined? It seems completely random, but it would probably be more user friendly to sort them by either category or name at first, until the user changes the sort order.