native integration with skills

[JarbasAl]

in OpenVoiceOS we are introducing what we call GUI extensions, these provide platform support for gui clients

this repo does not render the QML files provided by skills but instead requires "manual support" via new components

suggestion:

• create a new GUI extension under OpenVoiceOS implementing something similar to the homescreen in smartspeaker extension
• extend ovos-workshop resource file loading to allow .jsx and .css files
• extend gui interface to load .jsx instead of .qml when using the new "react-gui" extension, then skills can provide their own components

this will need more discussion for sure, i just stumbled upon your repo and immediately thought about how to support it, the architecture will need some more considerations but I'm hoping I piqued your interest!

Let me know if I can help and if this is something you would like

[alexisdiaz008]

in OpenVoiceOS we are introducing what we call GUI extensions, these provide platform support for gui clients

this repo does not render the QML files provided by skills but instead requires "manual support" via new components

suggestion:

* create a new [GUI extension](https://github.com/OpenVoiceOS/ovos-gui/blob/dev/ovos_gui/extensions.py) under OpenVoiceOS implementing something similar to the homescreen in smartspeaker extension

* extend ovos-workshop [resource file loading](https://github.com/OpenVoiceOS/OVOS-workshop/blob/dev/ovos_workshop/resource_files.py) to allow .jsx and .css files

* extend [gui interface](https://github.com/OpenVoiceOS/ovos-utils/blob/dev/ovos_utils/gui.py#L632) to load .jsx instead of .qml when using the new "react-gui" extension, then skills can provide their own components

this will need more discussion for sure, i just stumbled upon your repo and immediately thought about how to support it, the architecture will need some more considerations but I'm hoping I piqued your interest!

Let me know if I can help and if this is something you would like

Hey, yes, definitely something I've considered in the past and am willing to explore, open to discussion on how to direct efforts here, the current implementation is for my personal use, but I can see a lot of value opening this up to be a GUI extension for the community that can process QML files