"Bo Peng" <[EMAIL PROTECTED]> writes:

>> As far as I am concerned, I am going to stop here this discussion. I
>> am not going to make the changes. I am not going to strongarm Bo into
>> doing them. So in the end Bo gets to decide (which IMO shows how good
>> the "commit first and discuss later" method is, but of course I see
>> only one side of the discussion).
>
> Yeap, the first complete implementation wins. :-)

And this is a very sad state of affairs that designing an UI is done
in terms of who wins. 

>> - the shortcuts should use Qt GUI friendly notation, nobody cares
>>   about LyX internal notation
>
> You mean Ctrl-s instead of C-s? I do not see a big difference here.

This is how the GUI looks like to the user. It gest translated to
different languages. Mac OS users get the nice strange signs they are
used to instead of C- and M-. Windows users get their own version too.
And this is what is shown in the menus. Nobody is supposed to have any
idea that these M- and C- even exist.

> The problem is that lyx can not parse Ctrl-s, 

Why do you want to _parse_ that? We are discussing display here. And
KeySequence provides this output or the bind-file version of it at no
additional cost.

>> - the colors should go
>
> You proposed bold for new... what is the difference? 

Because people who are color-blind do not see the colors. 
http://www.stcsig.org/usability/newsletter/9910-color-blindness.html

Because you picked your own set of colors and nobody will agree they
are correct? Are we going to allow configuration of those colors? This
is mad.

> Note that there are two colors left. Green for user added shortcuts,
> and red for removed ones.

I know, you have too many types of actions. Do you expect _anybody_ to
remember what purple stands for?

> I can stop displaying removed shortcuts as well by removing the
> shortcut field, and there will be no revert for the removal of system
> shortcuts. I guess this somehow makes things simpler. I can do this if
> you prefer. Please confirm.

Anything that makes the interface simpler is good.

>> - the "<- Clear" button is not needed, clearing a text entry field is
>>   simple enough.
>
> That is Edwin's work. I even did not use the label.

OK.

JMarc

Reply via email to