New answers tagged tables
ISO 8601 Duration As mentioned in the answer by Crissov, the ISO 8601 standard defines a textual representation of a span of time in this format: PnYnMnDTnHnMnS, called Durations. In this format, the P marks the beginning. The T separates the days portion from the time (fractional day) portion, and is omitted for whole days. Examples: P1D = One whole ...
It seems to me that confusion occurs because there are 2 low-order places with both methods. You could take all the data to fixed 3 decimal places (or 1 decimal place) of an hour, using a decimal point, and rounded before display. Remember to keep the data accurate by doing the maths in integer minutes internally, so minor floating-point errors can't occur ...
One other solution could be to show the seconds as well. Since seconds will be changing quickly it will be clear that the times are continually changing. I don't recommend this solution but from the perspective of clarity, it works.
You can also show the minutes with a smaller font. On stopwatches, this is done for the seconds or milliseconds. download bmml source – Wireframes created with Balsamiq Mockups
The international standard ISO 8601 would suggest P04:00 or P4H. Its part on periods, durations or time spans and repetitions, though, is hardly ever followed – and you aren’t using its date format in the first place. JFTR Please note that 4h00 is not unambiguous, since some people tend to write clock times that way. 4h00m or 4h00min would be better. ...
Another possibility would be to add a "prime" mark at the end, as is sometimes (often in race times) used. Minutes and seconds would look like 4′33″, so a single prime is minutes, so use 1:30′ for an hour and a half.
You could use decimals. So for example: 90 minutes would be 1.5 hours instead of 1:30 3 hours and 45 minutes would be 3.75 instead of 3:45 This format is highly scannable and makes it easier to sum the values in your head.
A plus sign is sometimes prefixed to the time format indicate offset. It can also imply duration. For example: +4:00 +10:00 +4:00 +6:00 +0:00 +6:00
You are right to ask this question. It really depends on who your users are. In labor-intensive environments, users are often very familiar with the HH:MM notation for duration, so it's OK to use that format. But, I agree that even for those environments easy to get it confused with time. Is there a better way? Let's start with the existing solution. ...
You have multiple variables in your system. Like @Lauren Dankiewicz pointed out, you need to float some initial wire-frames and learn from user reactions. A simple tree mostly wont help you here, you'd need to mix and match UI metaphors to achieve the right amount of granularity without making it tedious for the end user. You could also check what all the ...
Answer seems to be highly dependant on the layout chosen, as per the sketch. Rather than add sticky headers to an existing design, you may want to redesign layout to support them. download bmml source – Wireframes created with Balsamiq Mockups
Using a reasonable fixed table height would be better than floating sticky headers (too distracting)
I've designed and completed some usability research in the financial services industry with huge, complex data tables. What I could conclude was people who wanted data in a visualized form would make decisions based on that, so that should be prioritized above tabular data (assuming you're designing data visualization comparisons well). My study was ...
I don't like the idea of allowing the in-row combobox to create an "apply to all rows" action. Although that might save you some layout space, it breaks the affordance of the control. It's clear to the user that a control inside the row is intended to manipulate the row. Having that control manipulate the table is visually unintuitive even if you label ...
I'd put them at the right if you must choose. Unless you really need to filter your data to make sense of it, I'd tuck it out of the left-gutter view most people scan with. I've also has some really interesting usability sessions that suggest filters/search are confusing for non-techy people whom may rather just scroll. This all depends on the size of your ...
If the table is the only element displayed on the page, filters should be in a right or left column. and for tablet/mobile, just above the page title.
why don't you just use check-boxes for deleting and arrows for actions, similar to this -> keep is as clean as possible and it does not take much space
Top 50 recent answers are included