For the BlackSwan Project we will at least need the functionality of the

• Segmentation
• Segmentation Utilities?
• MatchPoint: many plugins
  • which are needed? do we provide another, simplified registration plugin that uses match point functionality?
• Semantic Relations
• Render Window Manager
• Properties?
• new, own PointSet-Tool (with region growing) - from @kleina ?
• Statistics? Or do we provide our own, new statistics plugin view?

In T24775#131403, @kalali wrote:

For the BlackSwan Project we will at least need the functionality of the

• Statistics? Or do we provide our own, new statistics plugin view?

If we can avoid it, I would not use the (refactored) statistics view. With the rework Clemens and André are currently orchestrating, wie should have a solid Basis to do so.

• MatchPoint

I would refactor all plugins anyways ;)

Some plugins have their UI-classes in a xxUI-modules. From there it is not possible to access the QmitkNodeSelectionDialog since it's located inside the org.mitk.gui.qt.common-plugin. Is there any reason not to move the dialog to the QtWidgets-module?

Edit: The QmitkNodeSelectionDialog depends on the QmitkNodeSelectionPreferenceHelper which itself depends on berry plugins, so it cannot easily moved to the QtWidgets-module.
Do you have any suggestions?

Which xxUI-modules are you refering to?

The reason why QmitkNodeSelectionDialog is in a plugin is that this class makes use of blue berry preferences. To my knowledge blueberry is only available in plugins and not in modules (@kislinsk Please, correct me if I am wrong). Thats also the reason why the selection widgets are in a plugin, because the depend on the dialog.

E.g. SemanticRelationsUI, RenderWindowManagerUI etc., to separate a module's UI logic from other logic.
Yes, I identified the problem, too.

Currently I have a widget inside the SemanticRelationsUI-module, that has buttons to select nodes. These buttons can not open a QmitkNodeSelectionDialog since they cannot access it. Now I need to use a different technique to move the dialog-open-functionality to a corresponding plugin.