<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Add control grouping "labeling" to NB Tabbed Interface" href="https://bugs.documentfoundation.org/show_bug.cgi?id=134481#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Add control grouping "labeling" to NB Tabbed Interface" href="https://bugs.documentfoundation.org/show_bug.cgi?id=134481">bug 134481</a> from <a class="email" href="mailto:jmills59@yahoo.com" title="John Mills <jmills59@yahoo.com>"> John Mills</a> <pre>Hello Stuart, Thank you for that reasoned explanation,I however think we are talking about two two distinct ideas on discoverability. You refer to 'tooltips' and 'extended tooltips' and indeed if I hover my mouse over the icon I currently see the name of the icon and I think you mean in the future that I would see a more detailed explanation of the functionality when I hover the mouse pointer over the icon. This is not the point that I was trying to make before. If I want a particular function in any of the constituent applications and do not know the icon in the currently implemented 'tooltip' workflow/search I could potentially have to hover my mouse over every icon in all of the 'tabs' until I find the correct description/tooltip. This to me is cumbersome and inefficient. Don't get me wrong that is a very useful feature to have and I will be happy to see the extended descriptions, it will however not make me find the functionality I require to perform the given task any quicker. However, what I am explaining is for the icon groupings to have contextually grouped descriptions underneath. If I want design, for example, I need no knowledge of the icon pictorially, I simply navigate to the associated 'design' section efficiently and quickly. I would then use the 'tooltips' on a small number of icons to find the functionality required. I think both of these methods for discoverability should work in tandem for the benefit of the user. Tooltips only is not efficient. If there is a technical reason such as the translation issue you mention then I can appreciate the rational for your decision. However I do not understand the description 'clean "Tabbed" mode NB UI.' Is the tabbed compact mode NB UI 'cleaner' as it is smaller vertically? I think this is somewhat subjective based upon the end users needs and wants. As I commented earlier these descriptions underneath the grouped information sections could be made optional, my opinion is they are useful and add value to the interface by improving the speed and accuracy of discoverability by removing unnecessary requirements to memorize many icons. I hope that explanation makes sense? I think this also supports the UX-discovery principles on the design wiki. <a href="https://wiki.documentfoundation.org/Design/Principles">https://wiki.documentfoundation.org/Design/Principles</a> ux-discovery Users should be able to discover functionality and information by visually exploring the interface, they should not be forced to recall information from memory. [Source: Nielsen] Kind regards</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>