[Run][Plugin Manager] Additional settings: Definition of controls for additional settings

[htcfreek]

📝 Provide a description of the new feature

We have now implemented a plugin management for PT Run into the settings ux (PR #9872; Issue #5273). This includes the option to define additional settings (like disable drive detection warning) for each plugin.

For the first step we agreed, that we do this technically by defining an array of check boxes, save it in PT Runs' settings file and that the rendering of the settings is taken by the settings app. This is not really flexible and in the future we might have plugins that needs other ux controls than a checkbox. (Example: Websearch plugin with selection of search provider.) The described problem can also concern new built-in plugins.

I think we should ...

• allow more types of controls.
• move the definition of the elements out of PT Runs' settings file.
• strict define how the configuration file for the additional settings is formatted.

This is an example how the configuration file can look like in xml format:

<settingsGroup name="Result settings">
<checkbox name="example" default="on" settingsJsonString="ShowExampleResult" />
<radioGroup name="Show results of type" defaultRadio="1" settingsJsonString="ShowGameResult">
<radio order=1 name="all" description="example"/>
<radio order=2 name="games only" description="example"/>
</radioGroup>
</settingsGroup>

---

This is a remaining enhancement idea form issue #9655.

If you'd like to see this feature implemented, add a 👍 reaction to this post.

[crutkas]

This needs to be directly driven by requirements versus hypothetical.

[htcfreek]

This needs to be directly driven by requirements versus hypothetical.

How do you mean this? What do you think how it could work?