Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Design Discussion to provide field inputs/parameters as dropdowns #5

Open
ashwin100196 opened this issue Jul 17, 2021 · 1 comment
Open

Comments

@ashwin100196
Copy link

Hi @schlerp, I have been thinking it would be useful provide input fields with drop downs to the user. As a reference, I use bamboolib for personal projects and they do this very well. Link: https://docs.bamboolib.8080labs.com/documentation/getting-started

Started this issue to discuss on a design for implementation since the same design would be usable for the majority of the app, ranging from column name selection all the way to hyper parameters to aggregation functions like datetime format/resampling frequency etc.

Boolean parameters will still be kept as check boxes, as has been implemented for index in csv output block.

@schlerp
Copy link
Owner

schlerp commented Jul 20, 2021

So the front end is currently written in react using the material-ui library. This actually gives us some nice user interface elements including things like switches for boolean values and combo boxes with autocomplete. As I'm very new to frontend development right now its understandably a bit of a mess. So control wise we have access to all the ui elements we will need.

I would like to use https://material-ui.com/components/switches/ for boolean values.
for text fields i like the outline variant of these https://material-ui.com/components/text-fields/. These also can operate as combo boxes with autocomplete, or select boxes that allow choosing from a predefined set of values.
There are sliders for choosing numeric values from predefined ranges etc.

Have a look at the https://material-ui.com components and let me know what you think, id be happy to hear your thoughts and change any elements we think could work/look better a different way.

For things like autocomplete the issue really would be around how we setup the backend environment and expose that via the API to the frontend. This would allow us to include things like autocomplete for reading files into input nodes etc.

for storage should we use:

  • S3 buckets?
  • or a predetermined folder somewhere local?
  • both and have it as a configurable option?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants