Thanks all for the suggestions. Very enlightening.
To give a bit more context. Many of the help tips they want to
display are concerned with explaining to the customer the science
behind the control as opposed to explaining control X runs Y. The
applications are focused on geological and
The first idea sounds cool, but i can see why it was nixed, as it is
something i've never seen, and it would most likely require help
text to describe how to use the draggable question mark.
i too have to deal with complex pages on a legacy design requiring
multiple tool tips. I think having one
An old standard that I seem to recall is to have dotted underline
under some of the words. I don't know if anyone still uses this but
it might work. I have used a small box with a question mark in it
near each item but my pages were not very dense so it worked.
Just a thought.
Susie Robson
I wrote an (unintelligible) blog post about an idea for handling this -
having a single button that places a translucent overlay covering the
interface, which has helpful text directly on top of each element. Clicking
anywhere on the UI would then re-hide the translucent overlay. It didn't
get
Your gut is right, can you share any more context about the ui?
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://www.ixda.org/discuss?post=35373
Welcome to the Interaction
I agree that ?s all over is very busy. But how about *space* for them
which only gets filled with focus in or hover over a given control?
That would perhaps give nearly the same value with minimal added
clutter. (Perhaps = user test it.)
The first magically appearing ? might be odd, but
What about some info about the control(s) you want to give help for?
Is it a helptip system or a help guide you want to provide? In the
first case, I won't think of too much content: it is not the right
context for a multi-line tip. I like the idea of a more link but
I'd think of a different
I'd follow Alan Cooper's advice on this one: Make the interface give
the user data instantly, like the view screen fighter pilots use.
Make a toolbar that gives the user these messages. The user rolls
over a tool and the message toolbar lets him/her know what the button
is for.
Optimally your
Best helptips are no helptips: I do not agree with this just
because sometimes we are asked to solve usability issues generated by
others' UI designs. I don't see why we should provide an help system
if we recognise that the UI is not that natural and easy-to-use ;-)
For the legacy design, i
I have been asked to come up with an intuitive help method for tooltips
on a very complex dialog. I immediately thought of a question mark which
the customer clicks on and then drags over the interface, but that idea
has been nixed. Our competitors tend to put question marks next to every
main
How about a non-standard, multiline tooltip? Same simple presentation
as the standard tooltip, showing on mouseover with a reasonable
delay. See, for example, the way news story abstracts display upon
rollover of the headline in the CNN news gadget:
You might try a static info panel area instead. A very simple example
would be the way the browser status bar used to show links before you
clicked on them. If you want to see the same thing in use in
something that's probably more complicated than your dialog, check out
the integrated
PROTECTED]
11/07/2008 12:31 PM
To
[EMAIL PROTECTED]
cc
Subject
[IxDA Discuss] Good examples of Help Tooltips
I have been asked to come up with an intuitive help method for tooltips
on a very complex dialog. I immediately thought of a question mark which
the customer clicks on and then drags over
A good helptips is none helptips.
Cheers,
Jarod
On Sat, Nov 8, 2008 at 1:31 AM, Mark Pawson [EMAIL PROTECTED] wrote:
I have been asked to come up with an intuitive help method for tooltips
on a very complex dialog. I immediately thought of a question mark which
the customer clicks on and then
14 matches
Mail list logo
