Tag Info

New answers tagged

0

The idea behind a spinner, progress bar, etc. is to add the spinning element to your execution thread so when the operation starts the spinner shows up and when it ends, the spinner goes away. The way you are doing it seems to be wrong because you are not tying your spinner to the action itself and as result are adding an unnecessary delay to it. That ...


0

So, I bring up the spinner, and simply wait, oh, 0.6, 0.65, say, and only then actually call1 for the connection - which indeed then typically takes almost no time. What is the point of this? You don't even mention any reason at all (unless I missed it), which makes me assume you do this because the connection call can be very fast. Unlike the ...


0

The language in your wireframes doesn't seem to match how you're explaining things. It sounds like the thing a user needs to do to get from the full table to the "most interesting" view, is hide future dates. download bmml source – Wireframes created with Balsamiq Mockups Regarding the communication of future items, rather than mark every item, ...


0

Have you seen this in any production apps? (That is to say, I guess you'd have been on the development team - as you wouldn't necessarily know about it, I guess, as a user!) Yes, I think most of us have probably also done this because they like to see their clever little loader... but then move on. A loader should IMO only be used when something takes ...


1

I’ve dealt with the same kind of problem on a big project and discovered some key insights: While relative time selection is useful under many circumstances, it’s not a complete solution in every context, particularly under more technical circumstances. In a troubleshooting workflow, for example, “Earlier than 2 hours ago” can be close to worthless. Power ...


1

I suggest abandon using +/- way of doing this, but try to use start date and end date approach, but with relative dates: [start date][2d ago][end date][now] --> means "analyse last 2 days" [start date][undefined][end date][3h ago] --> means "analyse all data that arrived not later than 3 hours ago" [start date][2d ago][end date][3h ago] --> means ...


6

For controls used rarely, explicit is better than implicit If this widget were being used 100x a day, the answer might be an expert interface where the user can enter values like 10h8m, 1d23h5m etc. But, this is not your use case. You have stated that this widget will be used very rarely. In this case, it's much more important to make the interface ...


1

Personally, I have to say I find the plus and minus symbols somewhat unintuitive... to me, "earlier than minus 2 hours" is a double negative that combines to mean "later than 2 hours", or something :) Are you restricted to two fields? With a second dropdown at the end, you could be more explicit, e.g.: [up to ] [ 3h] [ago] -- means "up to 12:45" ...


0

I think your current approach carries a hefty cognitive load. You're anticipating the user being able to understand: That the scale is relative to the time right now That using a + or - alters the start or stop based on the time right now That they can specify time in days, hours and minutes with d/h/m Using your system, if I wanted a report that ended ...


2

The simplest solution I can think of is a numerical text input followed by a drop down for unit size - something like this: download bmml source – Wireframes created with Balsamiq Mockups


4

I think its a hard question to form one answer to. Pure theoretically, I'd suggest not to rely on the user to know these abbreviatons like h,d,s,... or at least try to lower some cognitive load by explaining the use cleary (as Don Norman likes to call it, put the knowledge in the world instead of in the head). From the moment you introduce a syntax (like ...


1

Edited answer: You're almost there I see you edited your question to show that the times appear in a grid. This is perfect, since a grid does exactly what the rest of this answer suggests. Even if the grid is "transparent" it is apparent. Your table follows a convention. It is clear. It could be a bit clearer, still. Why don't you experiment with: Remove ...



Top 50 recent answers are included