c# - User interface design for bi-directional searching of enumerations -
I have a file that stores the list of enumeration with its associated values. The following is an illustration of what the file looks like (instead of its original contents):
month Code>
I am writing a C # program so that the user can get permission to view animated values and their associated texts between them. In other words, they should be able to see the text with a value, and vice versa.
I wonder what is the best way to design user interfaces? I have several ideas:
- Two text boxes are user can fill in any of them and others automatically populate as user type. If the value is invalid, leave the other text box blank.
- Take a text box to fill the information in favor of the user, specify a radio button what information they are filling in the text box, an OK button that is pressed, the result or error Update text labels with message
- Similar to 2, but not ok button, just update the text label as the user type (i.e. control control. Kepress event).
- Have two separate screens (searching for calculations from one text, searching text from second to counting) and user flip between them by a tab or a button Use user input to display results or error messages, Take a text box for an OK button and a text label.
- Place two different areas on the same screen. Each area has the same format as 4. I thought I'd expect a GUI application, though it could be a bit slow and what is the problem to display if the user simply typed "S" and pressed OK Option 1 is maceresius but can be more interactive (answers show quick).
Sorry if this is not strictly a programming question, but I think this is a UI design problem that often comes in adequate if anyone has any industrial standards about best practices I know?
Thank you very much.
How many items do you expect to be in the list? If this is a small number, then perhaps < 100, I actually take the Tufte approach and display two well-designed table side-by-side (sorted by a value, by other means). Eye / brain connection can be parsed data faster than we know; I think that Tofe has claimed that every eye is capable of ~ 10 mb / sec.
If you have many types of data, however, I think that # 1 is your best bet, the largest number of form controls, and you can quickly recover data via AJAX or an inline array. Can get it. Make sure your instructional text is completely clear and concise.
The only downside to this approach I see is that it prevents users from viewing the related data sets and installing their own patterns. For example, if you tell me that 0 = Sunday and 1 = Monday, I can make a proper assumption that 2 = Tuesday. If a user understands the pattern, then I want to see it to be used for each individual value instead of using the form.
Comments
Post a Comment