On 5 Feb 2002, Jean-Marc Lasgouttes wrote:
> > "R" == R Lahaye <[EMAIL PROTECTED]> writes:
>
> R> Much better would be if a context sensitive help would open a
> R> documentation file and jump to the right spot automagically. A
> R> "Context Sensitive Help" entry under the help button could d
On Tue, Feb 05, 2002 at 02:42:29PM +0100, Herbert Voss wrote:
> while (true) {
> my position is not important for me, only the ones from
> the users...
> }
unfortunately we as developers have to second-guess what the users as a whole
want, and come up with good compromises. In particular mot
On Tue, Feb 05, 2002 at 01:23:50PM +, Angus Leeming wrote:
> It seems like you are in a minority of one here, Herbert. Here's my take on
> it:
I partly agree with Herbert - there is room for intermediate online help. But this
should
remain short and to the point.
WhatsThis context sensiti
On Tue, Feb 05, 2002 at 01:54:08PM +0100, Herbert Voss wrote:
> toolstips are one thing, every application has it more or
> less. They are okay, but you are _very_ limited in the
> length! The help-button gives you a help whuch is more than
> a tip, it explains some important interaction which th
> "R" == R Lahaye <[EMAIL PROTECTED]> writes:
R> Much better would be if a context sensitive help would open a
R> documentation file and jump to the right spot automagically. A
R> "Context Sensitive Help" entry under the help button could do that.
That's what I proposed with some labels adde
On Tuesday 05 February 2002 1:44 pm, Juergen Spitzmueller wrote:
> Angus Leeming wrote:
> > However, rather than define C_FormTexinfoFeedbackCB, setPreHandler,
> > feedbackCB for every class, you should make these methods part of the
> > FormBase collection of functions. Then the derived classes w
Jean-Marc Lasgouttes wrote:
> Knowing in which forms online help should be given is definitely a
> question of design, yes. It is a matter of user knowing immediately
> how to get help in a dialog.
Presently there is a problem if you quickly want to be remembered
how a certain feature works. Ope
Herbert Voss wrote:
> I never said that in all cases the help files are better than
> tooltips. And I never said that every gui needs a help button.
> But I said that the tabular-, the graphic-, the preferences-,
> a.s.o should have one.
> And don't tell me, that tooltips are really enough help in
> "Herbert" == Herbert Voss <[EMAIL PROTECTED]> writes:
>> A good help system is really needed, but I have to say I am not
>> sure your solution is a good help system.
Herbert> while (true) { my position is not important for me, only the
Herbert> ones from the users... }
... as long as you
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
>> [Hint] here is one: the tooltips are not accessible with the mouse
>> (I'm not sure this matters much, though).
Angus> What d'ya mean? Sure they are. Have you ever moved your mouse
Angus> over the preferences dialog?
I meant _without
> "Herbert" == Herbert Voss <[EMAIL PROTECTED]> writes:
>> So you say we should implement both and let people select one from
>> prefs? Yuck!
Herbert> cool conclusion ... the users can say: the help-buttons in
Herbert> _some_ of the guis are very fine (do more) or totally
Herbert> bullshit (
Angus Leeming wrote:
> However, rather than define C_FormTexinfoFeedbackCB, setPreHandler,
> feedbackCB for every class, you should make these methods part of the
> FormBase collection of functions. Then the derived classes will need
> only to override the virtual method
Angus, can you give me a
Jean-Marc Lasgouttes wrote:
>>"Herbert" == Herbert Voss <[EMAIL PROTECTED]> writes:
>>
>
> Herbert> Juergen Spitzmueller wrote:
>
>>>Developers have to decide what is good and bad ui-design.
>>>
>
> Herbert> you are kidding, or do you want to tell me, that one button
> Herbert> is a qu
On Tuesday 05 February 2002 1:31 pm, Jean-Marc Lasgouttes wrote:
> > "Herbert" == Herbert Voss <[EMAIL PROTECTED]> writes:
>
> Herbert> Juergen Spitzmueller wrote:
> >> Developers have to decide what is good and bad ui-design.
>
> Herbert> you are kidding, or do you want to tell me, that one
> "Herbert" == Herbert Voss <[EMAIL PROTECTED]> writes:
Herbert> Juergen Spitzmueller wrote:
>> Developers have to decide what is good and bad ui-design.
Herbert> you are kidding, or do you want to tell me, that one button
Herbert> is a question of design ...
Knowing in which forms online h
On Tuesday 05 February 2002 1:13 pm, Herbert Voss wrote:
> Juergen Spitzmueller wrote:
>
> > Developers have to decide what is good and bad ui-design.
>
>
> you are kidding, or do you want to tell me, that one button
> is a question of design ...
>
> > No one besides you knows better what user
Herbert Voss wrote:
> > Developers have to decide what is good and bad ui-design.
>
> you are kidding, or do you want to tell me, that one button
> is a question of design ...
It is of course not the button. It is the approach. But I think you
know this.
Juergen.
Juergen Spitzmueller wrote:
> Developers have to decide what is good and bad ui-design.
you are kidding, or do you want to tell me, that one button
is a question of design ...
> No one besides you knows better what users want when it comes to help.
aha ...
> But UI-design is a thing that i
Jean-Marc Lasgouttes wrote:
>
> Herbert> This is _absolutely_ user-dependent and it will be the best
> Herbert> way to let them decide which is more or less helpful!
>
> So you say we should implement both and let people select one from
> prefs? Yuck!
cool conclusion ...
the users can say: th
Herbert Voss wrote:
> toolstips are one thing, every application has it more or
> less. They are okay, but you are _very_ limited in the
> length! The help-button gives you a help whuch is more than
> a tip, it explains some important interaction which the toolstips
> can't. The next step are the
> "Herbert" == Herbert Voss <[EMAIL PROTECTED]> writes:
Herbert> toolstips are one thing, every application has it more or
Herbert> less. They are okay, but you are _very_ limited in the
Herbert> length! The help-button gives you a help whuch is more than a
Herbert> tip, it explains some impo
Juergen Spitzmueller wrote:
> IMHO a context sensitive help ("tooltips" like we have in preferences)
> is much clearer than a help button, which opens another dialog
> containing nothing else than (non-context-sensitive) tooltips.
>
> So I propose to replace the help stuff by context sensitive
On Tuesday 05 February 2002 11:28 am, Juergen Spitzmueller wrote:
> IMHO a context sensitive help ("tooltips" like we have in preferences)
> is much clearer than a help button, which opens another dialog
> containing nothing else than (non-context-sensitive) tooltips.
>
> So I propose to replac
IMHO a context sensitive help ("tooltips" like we have in preferences)
is much clearer than a help button, which opens another dialog
containing nothing else than (non-context-sensitive) tooltips.
So I propose to replace the help stuff by context sensitive hints. The
attached patch does this f
24 matches
Mail list logo
