GUI Extensions defines a couple of extension points for the KeY User Interface. It allows to add new functionality into the gui, without digging through the old UI code. It also should make the UI more consistent, decoupling dependencies and easier to implement new functionality.
General extension points¶
An extension is defined by an interface, which should be implemented by the new
functionality. This interface defines the methods needed to be successfully
injected into the UI. GUI Extensions are loaded and found via the
ServiceLoader facility of Java. Therefore, you should mention your extension
in the appropiate serivce file under
Every gui extension should be marked with
KeyGuiExtension and is only loaded
once. It does not matter on how many extension points it participate.
Different GUI extension should not depend on each other, as Gui Extension should loaded independent.
Basic Extension Metadata¶
Additional meta data can plugged to an extension by adding the Java annotation
Annotation because of accessible via the class w/o instantiation.
- Extension Points are now in
General UI facilities¶
KeYIcon introduces a way of icon management and configuration via
KeyStrokeManager reworked. It is now possible to define
a properties file.
Sharing Services accross UI extensions¶
Lookup a successor for a flexible mediator replacement based on
a service architecture, incl. Dependency Injection
- A common settings dialog should replace all existing setting dialogs.
- A component can register a
SettingsManager.getInstance()to participate in the default instance.
SettingsProvideroffers mainly a description, a panel, and a handler to save the settings.
SettingsProvidercan have children (
- An extension can announce a
SettingsProviderby declaring to be
- Existing settings were adopted.
Changes to settings: It is now possible to hook into the
proof-independent/-dependent settings by calling