asp.net：UI 设计最佳实践？
在我的 asp.net 应用程序中，我有一个表单，用户可以在其中选择一些技能（超过 40 种），并且每个技能可以定义他的技能级别（值从 1 到 10）。
我最初的想法是显示 1 个组合框，旁边有一个滑块。 每当用户选择一项技能时，其下方就会出现一个包含所有技能 + 滑块的新组合框，并且所选技能组合框 + 滑块旁边会出现一个删除按钮，以防用户想要删除之前选择的技能。
起初这似乎是一个好主意，但现在我正在构建它，它看起来有点奇怪而且不那么直观。
你们将如何实施这个？
In my asp.net application I have a form where a user can pick a few skills (there are over 40) and per skill can define his skill level (value from 1-10).
My initial idea was to show 1 combobox with a slider next to it.
Everytime the user picks a skill a new combobox with all the skills + slider appears underneath it and the picked skill combobox + slider gets a delete button next to it, in case they want to delete the previous selected skill.
At first this seemed like a good idea, but now that I'm building it it looks kinda weird and not that intuitive.
How would you guys implement this?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
使用附加输入进行多项选择的组合框不是一个好主意。你能列出技能吗（我知道40个已经不少了，但这取决于应用程序的使用情况）？我最初的想法是拥有一项技能、一个复选框（可以取消选中）和一个出现在侧面的级别滑块。
当然，UI 设计是针对特定应用程序和用户群的。不同的应用有不同的要求。
ETA - 基于评论，另一个选择是将任务分成两部分（说实话，这可能是该任务更好、更有效的解决方案。这是我的博士研究领域，所以我可能知道我在说什么）。您能否在一个页面上选择技能列表，在另一个页面上列出所选技能，并打开滑块（以及“删除”选项）。从可用性的角度来看，我认为这可能更容易。
Combo box for multiple selections with additional input is not a good idea. Can you list the skills ( I know 40 is quite a few, but it depends on the aplication usage )? Having a skill, with a checkbox ( that can be unchecked ) and a slider of level appearing to the side would be my initial thought.
Of course, UI design is very specific to a particular application and user base. Different applications have different requirements.
ETA - based on comments, the other option is to split the task into two pieces ( TBH, that would probably be a better and more efficient solution to this task. That is my PhD study area, so I might know what I am talking about ). Can you have one page to select the list of skills, and another to list the selected ones, with sliders on ( and "remove" options too ). From a useability perspective, I would think this might be easier.