Tag Info

New answers tagged

2

Not saying this is the "best", but the current version of MS Outlook shows the delete icon only when the mouse is hovered over the row: And then turns it to red when the mouse hovers over the delete button: Note that the icon they use is subtly different- the slightly "curved" X implies "delete/remove" as opposed to a straight X which in my mind is more ...


-1

You may use name and description columns and merge them all into a single table. Name is mandatory while description is optional.


1

You may use a hierarchical structure. If the risk is global then place it under the top level goal, if the risk affects only some events then place it under the affected events only. You can do something like the following :


0

Rather than mixing many icons into the table it may be easier to use them as the header label (with a tool-tip on hover), and a simple check mark to indicate that a user has this role. I think that this approach allows for uniform column width and will make the table far more scannable.


0

If your users will visit the list frequently and the roles will be maximum 10, then I recommend that you use icons and mouse over tooltips for their descriptions. Icons are much more superior than words for a quick visual scan. After a few interactions your users will learn the icons and their meaning. Otherwise if the users will not visit the list ...


0

If the list is so big, i think that multiple columns with icons is not functional. I prefer to add their roles with checkbox choice.


0

Simplifying your data when in a table is crucial to readability. When I make a front-end table, I use the same principles as if I would be doing a SQL table to some extent. If it were a database, you'd have a new item per role. instead of one enumerator that returned, or a csv. So in your table I would do that. What I think has happened to you here is you ...


0

In principal the use of icons (on their own) to convey complex concepts is a very difficult enterprise because they are prone to multiple interpretations, so would strongly suggest identfying larger groups of roles rather than specific roles. However, if you intend to use icons, you need to include labels to make sure that the right meaning is conveyed. ...


0

You say "could have up to 10"... But how many do most folks have? If most have 1 or 2 roles, you could show up to 2 icons plus a " more" link for those who need it. Another thought is maybe users could identify their primary role, then just display that icon with a link to "more" when needed. This way too, you are showing only the highest value info ...


2

You are right to be worried about the number of icons becoming too large. Unless you can find icons that are really obvious, this will become overwhelming for the user. You could try splitting the roles up into a small number of categories, and assigning an icon to each category. For example, you could have a "management" category represented by an icon in ...


0

The best option here depends on what your user needs to do. 1. If it's important to be able to quickly skim the list to find a Founder, it makes sense to put Founder in its own column like your second example. You can glance down any of the member type columns and quickly find the ones you're looking for. 2. If it's important to quickly learn about an ...


0

The problem with using icons is that you are requiring the user to have an additional cognitive load of trying to remember which icons relates to which user group and as the user scans down the table, he will no longer have the header as the textual indicator of what each icon stands for. Instead of going with icons, I would recommend going with a ...


0

I have recently worked on a project which required to display a lot of information in a tabular format with large number of columns. We followed the following approach - Horizontal scroll is inevitable. You have to use it when dealing with lots of columns. The thing which you can do is maximize the number of columns visible to the user at once. Sometimes ...


0

Quite often when users have a requirement to display loads of columns, what they really mean is that every individual user has a different subset of columns that are important to them. In this scenario it can be useful to let users configure their own column order and layout (i.e. they can choose what columns to hide), so each user can see exactly what they ...


1

After running into the same issues quite recently at work, I followed these steps to reduce horizontal size, and try to adapt the content to smaller (or wide enough) screens: Reduce font size from 1em to 0.9em. The change is slim, but enough to reduce up to 2-3 columns when you have a lot of them. Analyse exactly the priority of each columns, and start ...


5

From an accessibility point of view, if you rely purely on colour coding, the information provided by those colours ('verified', 'problem' and 'unclassified') may be inaccessible (or misleading) to people who are unable to perceive the differences between those colours, either because they are colourblind or are perhaps completely blind. It also makes the ...


1

Quick Answer If it's being provided just for call centre employees, have you asked them which of the two they prefer? Running some quick mock-ups past them would resolve your quandry pretty quickly. More Formal Answer If you've got two different UI paradigms that your team are arguing over, the only way to work out which is the better one is to test them ...


0

Do Not Repeat Currency Symbol Currency symbols are boulders along the road our eye takes in reading a table of numbers. Omit them from any series of data values. Embed the currency symbol in the column header, such as Total ($). Even better, embed the three-letter standard ISO 4217 code for the currency if there is any possible ambiguity in the context. ...


1

I think you should give a display of all of the days and the times of the notifications for each day. Group this list into 2 groups (one group for each week), then the times (AM/PM) beside each day should be clickable so they can be changed individually. This way they act as a status of the time set and as an actual control that is clickable. When tapped ...


0

Can it be like this? download bmml source – Wireframes created with Balsamiq Mockups


1

Here is an example solution, I suggest you keep the column width static. As having the whole table change width might be a bit unsettling (assuming that there are more columns).


0

If you don't want anything to clutter your rows all the time with icons (like a drop down menu arrow, a hamburger menu, 3 vertical dots or similar) I think your option here is to show one of those icons when the row is clicked. You will at some point need to tell the user that the row has options, and that is really the standard way of doing that. You can ...



Top 50 recent answers are included