New answers tagged input
The error message should probably include details of how to fix it too, with examples if possible. XML is not really always a user-friendly medium, especially when a strict XSD schema is involved. Is it possible to rethink this requirement, so that an alternative method is used, or perhaps allow the XML and/or XSD to be created via a nice UI?
I think part of making the error message clearer for non-specialists is to indicate what the user can do to fix it. Is there something they can check on? Someone they should contact? Documentation they can consult?
In any population, there will always be some outliers who don't do things the way most of the population does. Someone, surely, will fail to capitalize their name. What's the drawback, if users don't capitalize their own name? Do these names get used in a context where it might reflect poorly on the company? Do the names get used in legal documents or on ...
And why not have the possibility to insert a line at any place the user wants ?. If the end of the list is really bad place with bad ux for the user when he has got a huge list if you fix the field add on the top of the table while the user scroll he can reads his table and scroll in to check an existing value for example. And when he doesn't see the value ...
While forming a triple, you could have an "Actions" drop-down in the middle of the screen. One at a time, you could display selectable conditions or targets in a "cloud" around the selected action. If the items in these large sets can be compared to each other in some way, you could create a 2-dimensional mapping of them based on a dissimilarity matrix. ...
I would suggest to include (y/n) in the question itself, like this: Do you wear glasses? (y/n): If user enters a wrong answer, just display back the same question again. I believe this will be self-explanatory: Do you wear glasses? (y/n):5 Do you wear glasses? (y/n): .. What's your height? (cm):172
I agree with Paul. If you have chosen CLI, then I guess your users understand what should be entered. But manual or typo errors will occur. Humans make mistakes. Even for boolean inputs "yes" may not be accepted in place of "y". This scenario can extend to integers as well, where user might type a comma instead of a dot. The UI should let the user handle ...
Neither seem consistent The first big difference I see appears when the user have a list of maybe 15 items and they enter the page to add another one, I don't think it's a good idea to make them scroll to reach the New Item button. In the other hand placing the New Item button in the top isn't very familiar, plus the input point would descend 1 place to ...
The answer to the question is based on the fact that whats more important to your users, for them their old items in the wishlist might mean more to them and they would want them at the top (and add the new ones to the end of the list). The another approach, which I can say is more preferable in case of wishlist is, the newer the entry the more it is ...
Top 50 recent answers are included