Hi Leo,
At 00:17 15-10-2005, you wrote:
Hello everybody,
As Simon rightly points out, we should try and maintain the same
accelerator keys as in OOo 1.1.4 as much as possible, but on the other
hand we must make sure there is consistency between the various modules of
OOo, for example between Writer and Calc, but of course also the others.
Therefore I suggest that we do not split the work between different people
and if Henk agrees, I am willing to do this. If Simon has some general
rules in mind, please let us know.
Great!
I would suggest the following guidelines.
1) Try to keep the same accelerator keys as in OOo 1.1.4/5
2) Where necessary, make the accelerator keys in the various modules
consistent with those in Writer.
3) If another accelerator key has to be chosen, try if the first letter in
the item is available (e.g. ~Openen)
4) If the first letter in the item is already taken, try to choose the most
"logical" accelerator from e.g. the second letter (e.g. O~pslaan), or the
first letter of one of the words or syllables (e.g. Opslaan ~als, Af~drukken)
5) The menu options that would be most often used should get the "best"
accelerators.
Maybe a document can be organized as follows:
A table for each menu, identified by the module and the higher level menu
(e.g. Writer: top level menu or Calc: Bewerken)
First column: proposed menu items
Second column: menu items according to review build, including key ID (or
empty if no change is proposed)
Third column: 'x' if compatible with OOo 1.1.5, 'o' if not
Fourth column: remarks, such as an explanation where necessary.
I think that the first column would give us a pretty good overview of the
proposed accelerator assignments. Using the second column it is easy to
identify the changes that have to be made.
What about splitting the work for a first stage, making these documents for
each module? Henk and I could help with this. Then as a second stage you
could combine these documents, check for consistency between the modules
and make changes where necessary. After reviewing the resulting proposal
the necessary changes can be compiled and attached to an issue.
Vriendelijke groet,
Simon Brouwer.
>>> nl.openoffice.org <<<
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
