Tag Info

New answers tagged

2

Ok, I try to provide an answer in hope that it will encourage an expert to jump in, in case I tell nonsense. First of all I think the answer to your general question Should software attempt to interpret input such as 3,14 correctly? can only be unambiguously answered with a firm "it depends". I think the keyword in my above comment "every properly ...


2

From a visual point of view, 2 sizes is OK, different sizes for input fields is very confusing, and the same applies if you expect to input 2 characters and have room for 40. The user will wonder if they need to add something else in most cases, so visual hinting plays a role. Of course, like Chris commented, you need to keep in mind that under a certain ...


2

At least one example is in spreadsheets. Both Excel and Google Docs have Enter move to the next row and Tab move to the next column. If your the end user is familiar with certain types of data entry, using Enter may be more familiar to them. For example see: This is a fake example, but many financial documents are set up to be entered a single column at a ...


1

Design for the primary use case, then take care of secondaries I would guess that most users will know what they want to calculate, so they will come in, fill out two fields, then calculate the third. So this is the primary use case. Sometimes, users will change their minds or want to explore other variations, so they will switch fields or recalculate. ...


3

Three dependent values got me thinking about electricity and the rules of thumb for calculating power, current and voltage or current, voltage and resistance. In this Ohm's law calculator (at the end of the page) user has to enter two and only two values and click "Calculate" to get the third one. It's easy to click reset and to enter new values but if the ...


3

Use a non-destructive operation A merge company transaction is both complex and possibly destructive. A delete company operation, on the other hand, is destructive but not complex at all. You would need to test this solution with users but the following solution should have everything you're looking for broken down into a few simple and non-destructive ...


0

Based on your screenshot, the form page could do with a header below "Work Orders Management" which lets the user know whether they are currently editing of adding, wording along the lines of "Editing Work Order" or "Adding new work order". The Clear and Save buttons at the bottom, could do with being separated, physically or visually using different ...


6

User experience is different from data design Developers who move into UX often forget this important perspective change. Users don't think in terms of CRUD. They usually think in terms of what they want to get done. Some examples: For a micro blog, an author might want to create, update, and delete posts from the same convenient interface. For a ...


0

It can be on the same page. But all depends on requirements. Actually I've worked on form pages where the options are on same page as well as in different page (i.e) from the list page it will be redirected to an add/edit/view page. Delete will happen in list page. In case of same page, I would keep the form (add/edit/view) as hidden HTML div and will show ...


0

it's generally a good practice to not treat objects as "records" in a database, as they vary not only in number of properties, attached entities, etc, but also on importance, and their place in the workflow. An object might have a full-blown single page datasheet of its own in one workflow, and might be automatically created just from a string in the other ...



Top 50 recent answers are included