Tag Info

New answers tagged

1

You don't necessarily have to go with a button but as a user, I'd definitely like a click target that's bigger than a single number. You could make the whole cell clickable. If you want buttons you could make your header "Sessions/Calls" and then use a single cell and make a button group with sessions on one side and calls on the other. The "right" answer ...


4

Until I read your question, I hadn't even noticed the totals at the top. That alone indicated to me that the subtotals on the top are not clear. Additionally, here are some reasons why your totals should be placed at the bottom: Users read table data from top-to-bottom. Totals are an equation. Relating to the previous point, the user will best interpret ...


0

A way to use filters in defined columns in a table list view is to turn the table headers to filters and apply them accordingly to filter results


0

I second Sherwin's answer. Leaving as an answer instead of a comment so I can include an example.


0

I'd agree with most of the answers here and use a background colour and text colour change to indicate read only cells but from a web accessibility point of view you should also add additional non-colour based indicators such as an icon or text decoration to indicate which rows are read only.


1

I'd recommend the opposite: mark the editable cells as that is the unusual behaviour for tables. You could easily do this by adding a darker internal border to the top and right to make those editable cells look more like text input fields (an accepted pattern for editable text areas). However, if you are stuck on marking the field the user cannot interact ...


0

If you are using zebra striping for your rows having yet another bg colour row for disabled might be a might too much on the eye. In this instance you could change the font colour to be greyed out or a hightlight colour for the disabled rows. You can also change the cursor to not allowed:


0

Actually we also met such problem with too much data display in a table and user requires to see more columns directly instead of horizontal scrolling. What I know possible solution and what we also tried in our design: Try shrink the column width, like brief the wording or value. Brief view with expanding option, to allow user to view more details when ...


0

Always start by asking what users need to do with the data Do they need to go into a specific record to look up info or make edits or bulk edits? Put in easy search & filtering. Determine what are the general context users start with when it comes to finding data. Do they do a specific search (e.g. name, email, phone #) or by ranges? (e.g. by city, ...


0

Basic requirements I'd second everything scunliffe said. Sort and filter are critical. Pagination is once you get past 100 or 1000, depending on the data and speed of your service. You mentioned supporting search and query-building, but it deserves repeating that simple search is a given. On the point of pagination, it might help to think of it in database ...


2

Managing a list of anything... that is over ~50 items is tricky unless you have (or in this case provide) the right tools. Paginate the results - seeing more than ~100 of something on a screen is not very usable (If the user needs to see a larger set/all at once, provide an export option where they can manipulate the data externally) Sorting - provide ...


4

If the user has that large number of entries, I think is a better idea to sit the final user and get the requirements of the task that he is actually trying to do. I don't have all the context but what is he trying to achieve: If the user has to review all entries one by one (for example an accountant needs to review all the balances to see what is not ...



Top 50 recent answers are included