Bug 72285 [KeyBindings] registry: Cannot assign keybinding to general views
It seems the views have to do something special to show up on the "Views" keybinding list. It would be nice if all views showed up automatically. Of course then (or even now) there would be so many views that the current level of grouping is not sufficient.
bundles/org.eclipse.jface/src/org/eclipse/jface/bindings/Binding.java
* locales.
 * </p>
 * <p>
 * It is also possible to remove a particular binding. This is typically done as
 * part of user configuration (e.g., user changing keyboard shortcuts). However,
 * it can also be helpful when trying to change a binding on a particular locale
 * or platform. An "unbinding" is really just a binding with no command
 * identifier. For it to unbind a particular binding, it must match that binding
 * in its context identifier and scheme identifier. Subclasses (e.g.,
 * <code>KeyBinding</code>) may require other properties to match (e.g.,
 * <code>keySequence</code>). If these properties match, then this is an
 * unbinding. Note: the locale and platform can be different.
 * </p>
 * <p>
 * An example might be helpful. For the example, I will use the KeyBinding
 * concrete subclass. Image you have a key binding that looks like this:
 * </p>
 * <code><pre>
 * KeyBinding(command, scheme, context, &quot;Ctrl+Shift+F&quot;)
 * </pre></code>
 * <p>
 * Now, on GTK+, the "Ctrl+Shift+F" interferes with some native behaviour. So we
 * decide we need to change it.
 * </p>
 * <code><pre>
 *      KeyBinding(null,scheme,context,&quot;Ctrl+Shift+F&quot;,gtk)
 *      KeyBinding(command,scheme,context,&quot;Esc Ctrl+F&quot;,gtk)
 * </pre></code>
 * <p>
 * Bindings are intended to be immutable objects.