Is your feature request related to a problem? Please describe.
It is fustrating for users and developers to install additional libraries like XenInfo, InfoStats 2, et al.
Describe the solution you'd like
An integrated widget data solution, which can be disabled if not wanted by the user. This should widgets that rely on: GroovyAPI, InfoStats (1 and 2), XenInfo, and Exo.
Support for WidgetWeather is a stretch goal. Support for it can be started with supporting InfoStats 1 without writing any files to the filesystem; i.e., interposing resource loading.
Describe alternatives you've considered
XenInfo cannot be integrated directly due to licensing restrictions, and updating InfoStats 2 is not particularly viable (perhaps?) -> a public API-based solution is needed to prevent future breakage.
Additional context
NepetaDev is happy with the idea of integrating Exo, provided that any code will fallback to any user-installed version of Exo if available.
Is your feature request related to a problem? Please describe. It is fustrating for users and developers to install additional libraries like XenInfo, InfoStats 2, et al.
Describe the solution you'd like An integrated widget data solution, which can be disabled if not wanted by the user. This should widgets that rely on: GroovyAPI, InfoStats (1 and 2), XenInfo, and Exo.
Support for WidgetWeather is a stretch goal. Support for it can be started with supporting InfoStats 1 without writing any files to the filesystem; i.e., interposing resource loading.
Describe alternatives you've considered XenInfo cannot be integrated directly due to licensing restrictions, and updating InfoStats 2 is not particularly viable (perhaps?) -> a public API-based solution is needed to prevent future breakage.
Additional context NepetaDev is happy with the idea of integrating Exo, provided that any code will fallback to any user-installed version of Exo if available.