Future plans for plugin

[nyakowint]

This is not an issue, simply writing down what i plan to do later

• UI3.0
  • Investigate whether injecting the plugin via BepInEx is still necessary.
    • This will depend on whether web app support includes the ability to interface with C# (in the style of OVRTK Module Plugins)
    • Even if it does, it still probably will be as patching methods directly gets us the closest to desired behavior as possible.
• Closer Future
  • Transform Keyboard OSC into a pseudo-webapp.
    • I have not been able to figure out Click events are not sent to bar's overlay instance(?) #3 that well as it seems to be an issue with my canvas duplication, camera positioning (not sure how to make it any better), or some other factor.
    • This will bring the following benefits:
      • The limitations of unity are (mostly) no longer an issue; the clicking issue i mentioned earlier is because unity overlays are funky magic i dont understand
      • Everything you can do in a webpage is possible now
    • And the following disadvantages/caveat(s):
      • Vuplex Webview might behave weirdly. haven't tried it beyond the overlay's own UI webpages
      • Having to now communicate over a websocket urrrgggh; may not matter much seeing how ^ is pretty responsive
        it for now, may add more as i think about it
  • 06/09: I have made progress, though it may not be necessary given the below knowledge and timing.

01/22:

• Currently in the overlay webviews seem to use touch input only, and all keyboard shortcuts do not trigger to the webview. (tested by loading google in the settings overlay)
• focus on the webview seems to randomly break, maybe what's causing the above issue

06/09: