Add support for tuning plugins written in Java
- Dominant language
- Java
- Stars
- 287
- Forks
- 172
- PR merge metrics
- No merged PRs in 30d
Description
There are many tuning methods currently that either rely on running an executable or performing specific actions on an IP address. While there are plugins for Windows and Linux that support the case of an executable which can then also be used to perform an IP address oriented solutions, it's very challenging for non-tech savvy users to configure these plugins correctly.
I am working on an interface that can be used for this purpose and will allow normal plugins to register and unregister tuning plugins. The interface distinguishes between different devices by an integer ID so that it's completely compatible with how tuning is currently done. Plugins are determined to be Java instead of SFIR by checking a map of the registered Java tuner plugins. If it's not on the map, it's assumed to be SFIR. The API can also resolve the device ID to a more descriptive name as provided by the plugin. This gets around what would otherwise be a very limiting level of descriptiveness for Java based tuning devices.
My thoughts are that the Java tuning methods can be mixed with the SFIR plugins in the UI and if the plugin name matches the Java tuning plugin name when selected, it allows you to select a device from a list of the device ID's resolved to descriptive strings as provided by the plugin. If the list is empty, it will tell you to configure the associated plugin. I think it would be nice for that to go one step further and allow you to go directly to the plugin configuration from there, but I don't see how a plugin interface can find itself. SageTV wraps the plugin, so at least from what I've seen, you'd have to get all of the plugins and then find the one that matches your plugin or is there a much easier way to do this?
Contributor guide
Assessment
This issue has not been assessed yet.