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
Is your feature request related to a problem? Please describe.
There are plans to add many more Providers other than the Docker Provider to Daytona. The properties they need for configuration of e.g. VM characteristics such as the OS/arch combination need to be strictly defined in a specific format like image name, build name+version etc.
These values are hard to guess for the user and "recognition over recall" would be necessary to ensure good UX. This is an easier task for web apps than terminals because of the interactivity regarding dynamic substring-based suggestions when typing in the input values and simple and efficient dropdown components.
We need to research a way to implement this kind of UX enhancement that would combine the suggestions from a fixed set of suggestion strings (from a e.g. provider-specific config file) as well as allowing custom input for more specific entries.
This kind of component should be made as a custom Charm piece that is similarly designed to the existing TUI and should work well with any input type combination from a predefined provider config format.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
There are plans to add many more Providers other than the Docker Provider to Daytona. The properties they need for configuration of e.g. VM characteristics such as the OS/arch combination need to be strictly defined in a specific format like image name, build name+version etc.
These values are hard to guess for the user and "recognition over recall" would be necessary to ensure good UX. This is an easier task for web apps than terminals because of the interactivity regarding dynamic substring-based suggestions when typing in the input values and simple and efficient dropdown components.
We need to research a way to implement this kind of UX enhancement that would combine the suggestions from a fixed set of suggestion strings (from a e.g. provider-specific config file) as well as allowing custom input for more specific entries.
This kind of component should be made as a custom Charm piece that is similarly designed to the existing TUI and should work well with any input type combination from a predefined provider config format.
The text was updated successfully, but these errors were encountered: