How qupath/qupath works
Main components
• Core Modules: There are several “core” components. For example, “qupath-core” and “qupath-core-processing” contain the central libraries for image analysis, segmentation, detection algorithms, ROI tools, measurements, and data handling.
• Application Module: The “qupath-app” package forms the entry point for the executable application that ties the core processing, GUI, and extensions together.
• GUI Module: “qupath-gui-fx” contains the code for the Graphical User Interface (using JavaFX) including menus, toolbars, image viewers, dialog components, and other interactive elements.
• External Interfaces: Integration points to external software (for example, ImageJ and Image.sc forum links) and external APIs often come through plugins.
Architectural Patterns & Design Principles
• Plugin-based architecture, suggesting that the application can be easily extended for new file formats, processing techniques, or integration functionalities.
• Use of convention-over-configuration in build scripts (as seen in the “buildSrc” module’s Kotlin and Java convention files).
• Point out that many of the sub-components follow a layered architecture: user presentation (GUI) on one layer, business logic (core processing, algorithms) in the middle, and extension/integration plugins at a peripheral layer.
• The system also makes use of dependency injection/registration for plugins (check for use of “service” files in META-INF services).
Relevant Technologies and Frameworks
• Java and JavaFX (seen in qupath-gui-fx)
• Gradle (build scripts in build.gradle.kts and buildSrc)
• Integration with third-party libraries (e.g., ImageJ, Bio-Formats, OpenSlide) is supported via specific extension modules.
• The modular system may also use Java’s module system (module-info files are present) for controlling strong encapsulation.