incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ariel Constenla-Haile <>
Subject Re: [code] keyboard accelerators for main menus are no longer working on trunk
Date Thu, 05 Jul 2012 13:06:08 GMT
On Thu, Jul 05, 2012 at 01:14:09PM +0200, J├╝rgen Schmidt wrote:
> On 7/5/12 12:01 PM, Ariel Constenla-Haile wrote:
> > On Thu, Jul 05, 2012 at 06:56:14AM -0300, Ariel Constenla-Haile wrote:
> >> I'll add the shortcuts in a while, 
> > 
> > done in revision 1357534, please checkout. Only shortcuts for the
> > MenuBars, 12 commands.
> the reasons and they way how you do it make of course sense to me and
> the only point I want make is that it is a bigger change that directly
> effect our users and their daily work with the office.

Just to be clear, people don't have to mix two things:

- keyword shortcuts, some of them are set by the system, others can be
  customized by Tools - Customize... - Keyword
  A keyword shortcut is a set of key that invoke a function, for

  Ctrl+X - Cut
  Ctrl+C - Copy
  Ctrl+V - Paste

- keyword mnemonic is an underlined character that indicates which key
  to press to activate a command in a menu or navigate through a dialog


In order to activate the Cut command you have to activate first the menu
Edit; on the other hand, keyword shortcuts are straight forward.

As you see in this example there is no relation between keyword
shortcuts and keyword mnemonic. Though in some cases we may want to keep
this relation:

 ~Print - Ctrl+P
 ~Open  - Ctrl+O
 ~Save  - Ctrl+S

This has to be decided (by UX people, I guess).

> We have to ensure that we explain and communicate potential changes very
> well. Ideally we will have no changes for the most important short cuts.
> Make the shortcuts more consistent over all applications is of course a
> very good idea and it definitely makes sense.

Here the current situation is rather chaotic:

MODULE                      Commands    Label has ~

BasicIDECommands.xcu            0           0
BibliographyCommands.xcu        9           5
CalcCommands.xcu                243         186
ChartCommands.xcu               112         52
DbuCommands.xcu                 79          5
DrawImpressCommands.xcu         271         124
GenericCommands.xcu             762         178
MathCommands.xcu                28          16
StartModuleCommands.xcu         26          22
WriterCommands.xcu              370         121

These statistics are from AOO34 branch. I couldn't find a specification
on the topic, but looking at the logs it seems older labels have ~,
while the new tendency was to let the automatic mnemonic generation do
its job.

> I think the most important point here is the communication to our users.
> If in the end shortcuts will change we have to explain it and have to
> make clear the advantages in the long term.
> We also have to take care of the help and other documentation.

Only keyword shortcut are document on the Online Help. Keyword mnemonics
are only mentioned as a way to activate menus (search for "Calling Menus
With Shortcut Keys"), but of course they are not documented, it wouldn't
make any sense. So no, there are no modifications to the Help or any
other documentation I'm aware of.

> And of course the key accelerators are important for accessibility.

Keyword mnemonics will still be there, generated automatically or
hard-coded. Any way, I doubt this is going to have a big impact on the
user level, as most of the command's label mnemonics are currently
generated automatically, as you can see in the table above.

> >> now that you seem to miss them. Quite
> >> strange nobody notice/asked/complained before, it makes me wonder if
> >> anyone is really using trunk builds (nobody complained about the changes
> >> on the About dialog either ;) ).
> I noticed the changes but haven't found the time to take a closer look
> on it ;-)

Some changes are "documented" in the bug:

Ariel Constenla-Haile
La Plata, Argentina

View raw message