Rather than the current system of Startup/Keys.java, which is not very user-friendly and is difficult for modules to add to, suggest:

- modules and the IDE core at install time just make whatever bindings they wish to the global keymap

- IDE core saves the keymap as well as it can, i.e. stores on disk a list of pairs of shortcut text and the serialization of the Action, if it is instanceof Serializable; note that for SystemAction, t

his will work fine, and only the class name will need to be stored -> representation is compact

- somewhere under Session Settings, say a node Keyboard Shortcuts, with a single property "keymap" which contains the map; customizing brings up a dialog similar to that used for the Editor, except th
at instead of a fixed list of actions, any InstanceCookie instanceof Action instanceof Serializable present in Actions, Menu, or Toolbars folders would be presented as options, as well as any such act
ion already in another binding

- or, the node could have subnodes, one for each binding, ability to change keystroke on a node property (custom prop edit to permit sample input), can delete subnodes, or paste an appropriate Instanc
eCookie from elsewhere (maybe permit stuff with ExecCookie too, like menus and toolbars do...?), paste action would prompt for the keystroke to use (incl. after copy from another binding), node would
display action display name and keystroke text

- whole thing could if desired be made a module!