You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want certain parameters to be exposed to the user as something they can tune themselves or chose amongst options. For this we envision as settings menu accessible through the interface (some type of gear icon on the top right).
We need to first think about the general way we want to enable this.
We probably want the user's setting to be in Firebase so they are remembered. We might want some sort of Javascript global corresponding to each setting variable to be set to the user's preferred value when the connection to the Firebase is first made in the beginning. Setting should be updated whenever the user changes them.
Make it programatically easy to add new setting (i.e. should not need to copy paste a bunch of HTML, but instead just call one function with new parameters specifying parameter type and interface type (slider, radio button, text, color picker, etc.)). I have some code from EMAR we could reuse.
Have some good defaults for each parameter for new users.
I don't think we want settings to be a separate HTML page, but rather have them overlaid or re-render the page without loosing all the JS context. We could just use Bootstrap Modal.
This reminds me we now need to switch to having users log in, rather than be anonymous users. Will add a separate issue for that.
Some things to include in settings off the top of my head (keep adding to this thread as we think of them):
Torque feedback sensitivity
Continuous action update frequency
@kaviMD let me know what you think about how to implement settings.
The text was updated successfully, but these errors were encountered:
I made a rough version of this by hiding away some things on the interface into a Modal overlay that can be opened from a 'settings' button. Will improve later.
We want certain parameters to be exposed to the user as something they can tune themselves or chose amongst options. For this we envision as settings menu accessible through the interface (some type of gear icon on the top right).
We need to first think about the general way we want to enable this.
This reminds me we now need to switch to having users log in, rather than be anonymous users. Will add a separate issue for that.
Some things to include in settings off the top of my head (keep adding to this thread as we think of them):
@kaviMD let me know what you think about how to implement settings.
The text was updated successfully, but these errors were encountered: