We should allow to define all UI interaction elements / events which can be used to trigger an action in PKS-Edit using configuration files:
the menubar
context menus
keyboard bindings
mouse clicks
toolbar buttons
Action bindings should provide an optional action context in which they are available (e.g. an action may be only available in markup wysiwyg mode).
This will allow users to fully customize PKS-Edit to the desired behavior.
The corresponding configuration files should use JSON format in compliance to other configuration options. A default configuration (maybe multiple to mimik different popular editors and IDEs) should be provided, which can be extended / modified by users.
We should allow to define all UI interaction elements / events which can be used to trigger an action in PKS-Edit using configuration files:
Action bindings should provide an optional action context in which they are available (e.g. an action may be only available in markup wysiwyg mode).
This will allow users to fully customize PKS-Edit to the desired behavior.
The corresponding configuration files should use JSON format in compliance to other configuration options. A default configuration (maybe multiple to mimik different popular editors and IDEs) should be provided, which can be extended / modified by users.