Re: [platform-ui-dev] RFC: Key Bindings Proposal (end date = Dec 14, 200

[Dirk_Baeumer@xxxxxxx]

I don't agree with the statement that the short cuts must be consistent over all editors and that
users expect this behavior. Here are my reasons:

- if we embed an editor using OLE the short cuts aren't consistent either. For example if we load a Word document
  the short cuts will be different from the once defined for the rest of the Eclipse editors.
- the same is true if we launch an editor as an external tool.

Since we can't be consistent in this cases we should not try to be smarter in the others. 

IMO developers are used to different editors and their short cuts. So if I edit an HTML file using a special HTML editor I know that 
Ctrl+I is a short cut for Italic and if I edit a Java file using a special text editor an know that Ctrl+I means indent. What I think is important
that short cuts stay the same when I use the same type of editor (text editor A and text editor B). But if I use a special editor for special 
editing (like a special HTML editor) I want special shortcuts for special things. Otherwise I would use a normal text editor.

Dirk

Simon_Arsenault@xxxxxxx Sent by: platform-ui-dev-admin@xxxxxxxxxxx 12.12.2001 18:00 Please respond to platform-ui-dev

To:        platform-ui-dev@xxxxxxxxxxx         cc:                 Subject:        Re: [platform-ui-dev] RFC: Key Bindings Proposal (end date = Dec 14, 2001)

I understand your point of view.

In the proposal, I talk a little about this issue. We've decided to go the
route of Key Binding Set is king! That is, if Ctrl+I is assigned to the
common action id "Increase Indent", then that is what it will do in the
HTML editor (the set will provide another accelerator key for the common
action id "Italic").

Here is our reasoning. We believe applying the Key Binding Set all the time
will be more consistent to the user. It is a well documented fact that
users take time to learn accelerator keys and they get confused when it
changes between editors for the same type of action. Given the user in
Eclipse will be switching editors often, it would be a lot for the user to
note in which editor he is and ajust his/her thinking of what the
accelerator keys are now.  Maybe we are totally wrong here with this
assumption - that will be something that usuability tests will determine
(Julian, if you have any comments or data on this, please let us know so we
do not go down the wrong path).

As for your examples, if someone is using the "FrontPage" set, then most
likely the user is spending most of his/her time in the HTML editor. So
going to another editor is rare and therefore will probably be happy with
the global key binding idea.

If we allow editors to somehow override what the key set defines, then how
would this be shown to the user? Yes, actions that are in the menu could
have the accelerator text changed as the editor is activated but that is a
usuability no no as there is no feedback to the user unless he/she opens
the menu. There is also the problem of how much of the key binding set can
be overriden. Is that dependent on the "type" of key binding set (emac
users would probably not appreciate this...they want their emacs
accelerator keys all the time)

Simon :-)



                                                                                                            
                    "Randy Hudson"                                                                          
                    <hudsonr@xxxxxxxxxx>           To:     platform-ui-dev@xxxxxxxxxxx                      
                    Sent by:                       cc:                                                      
                    platform-ui-dev-admin@e        Subject:     Re: [platform-ui-dev] RFC: Key Bindings     
                    clipse.org                     Proposal (end date = Dec 14, 2001)                       
                                                                                                            
                                                                                                            
                    12/12/2001 11:26 AM                                                                     
                    Please respond to                                                                       
                    platform-ui-dev                                                                         
                                                                                                            
                                                                                                            



After seeing your two examples of FrontPage and Interdev I realize that a
single set of key bindings for all editors isn't what the user wants.  For
source code, I want Ctrl+I to be Indent, but for HTML I want ctrl+I to be
Italics.  Making "Indent" for source editors use something other than
Ctrl+I because WYSIWYG editors use it for Italics would be a mistake.

I suppose WYSIWYG editors could still respect some of the key bindings that
are used in source editors, like "End of line", but it might ignore others,
like indent.  However, you have to define all key bindings or none.  If you
define just a subset, and the Editor has to supplement that subset, how
does it know to avoid conflicts?

Maybe there would be specific key-bindings for WYSIWYG source too, like
Enter maps to newline <BR>, while Shift+Enter maps to new paragraph <P>.




                    David_Springgay@xxxxxxx

                    Sent by:                      To:
platform-ui-dev@xxxxxxxxxxx

                    platform-ui-dev-admin@e       cc:

                    clipse.org                    Subject:     Re:
[platform-ui-dev] RFC: Key Bindings Proposal (end date = Dec 14, 2001)



                    12/12/2001 10:01 AM

                    Please respond to

                    platform-ui-dev







If I am correct, the goal of the key binding proposal is to remap the
accelerators for global actions + editor actions.  For instance, you may
apply Emacs keybindings to the environment.  Emacs is more than just Find,
Save As, etc.  It also involves go to end of line, indent, Capitalize,
Upper Case, Lower Case, Bookmark, Jump to Bookmark, Goto Line, etc, and so
application of Emacs keybindings would also effect the editor actions.

There would be a single, dominant set of key bindings.  This would override
the accelerators defined in an editor, where the editor contributes one of
the common actions.

For instance, if you're a java developer who is familiar with MS Interdev,
you may choose the MS Interdev key bindings.  These key bindings would work
in the java editor,as well as the Html editor.  If you're an html
developer, who is familiar with Front Page, you may choose the Front Page
bindings.  These bindings would override your html editor, as well as your
java editor.  A single set of keybindings should work everywhere, and that
set should be chosen by the user.

Dave

_______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-ui-dev




_______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-ui-dev