Re: Gtk version getting closer

[Karl Eichwalder]

Eli Zaretskii <address@hidden> writes:

> Where the menu item's text is self-explanatory, there usually is no 
> tooltip that pops up.  In other words, tooltips for menu items should be 
> defined only where they are really needed.

That's even worth ;)  If you want to sell a product consistency is an
important issue.  The ideal goal should be: all or nothing.  If
tooltips appear only now and then, the user might think there is
something broken.

> You should be able to do a "C-h k", then click the menu item and get its 
> explanation.

Sure, that's a good way for the advanced user (to be more precise: for
the keyboard user).  You are not going to convince the mouse user he
wants to learn those key combos ;-)

> Another C-h function jumps to the manual for a description of any key,
> but the problem in using this with menu items is that menu items are
> generally not described at all in the manual.  So this is a
> documentation problem rather than a functionality problem;

Yes and no.  For the moment it would be good enough if Emacs would jump
to the documentation of the function; just print a message want you
intend to do.

> if someone writes an appendix for the manual with the description of
> all the menu items, it would be instantly available for the purpose
> you want it.

Sounds useful.  Maybe, I can spend some time on it next year.  Is it
okay to write it in German and to wait for someone to translate it?  Or
shall I try it in English and hope for corrections?

-- 
address@hidden (work) / address@hidden (home):              |
http://www.gnu.franken.de/ke/                            |      ,__o
Free Translation Project:                                |    _-\_<,
http://www.iro.umontreal.ca/contrib/po/HTML/             |   (*)/'(*)