This gadget creates a single UI layer that all gadgets can use to offload their own settings and configuration into. Each new gadget will see it’s settings UI placed within GCM and listed below the one before it in the left hand menu, along with any sub menus. Selecting a gadget will open it’s settings on the right side.
GCM would have UI features like a left hand list of gadgets along with any needed submenus and a search option, sliders, incremental adjustment, toggle adjustment, drop down menus, tooltips, and checkboxes. All settings are saved in a common config that all gadgets have access to. The gadget also has a desktop UI as a fail-safe and easy way of configuring multiple gadgets at once.
Gadget developers can use this gadget to offload the work of making a settings UI. But for users this also makes finding the settings/configuration for any app easy to do. This is also useful because misconfigured settings can make VR applications glitch out, fly away, or otherwise become unusable; this allows users to troubleshoot in this UI.
Assuming that you're on the team, what other skillsets would you need to make this project happen over a couple days of hacking?
I am not experienced with coding, I’m just trying to provide the concept for consideration.
What will be the toughest part of building this gadget?
Making a fully featured UI is the hardest part of this gadget, with all necessary features like tooltips and sliders that are also highly usable.
What would this gadget do?
This gadget creates a single UI layer that all gadgets can use to offload their own settings and configuration into. Each new gadget will see it’s settings UI placed within GCM and listed below the one before it in the left hand menu, along with any sub menus. Selecting a gadget will open it’s settings on the right side.
GCM would have UI features like a left hand list of gadgets along with any needed submenus and a search option, sliders, incremental adjustment, toggle adjustment, drop down menus, tooltips, and checkboxes. All settings are saved in a common config that all gadgets have access to. The gadget also has a desktop UI as a fail-safe and easy way of configuring multiple gadgets at once.
This is inspired by the Mod Configuration Menu from the Fallout community: https://slack-files.com/TPD5V23JT-F01BDB9414L-ba4f532d84
Who would use this gadget?
Gadget developers can use this gadget to offload the work of making a settings UI. But for users this also makes finding the settings/configuration for any app easy to do. This is also useful because misconfigured settings can make VR applications glitch out, fly away, or otherwise become unusable; this allows users to troubleshoot in this UI.
Assuming that you're on the team, what other skillsets would you need to make this project happen over a couple days of hacking?
I am not experienced with coding, I’m just trying to provide the concept for consideration.
What will be the toughest part of building this gadget?
Making a fully featured UI is the hardest part of this gadget, with all necessary features like tooltips and sliders that are also highly usable.