It would be worth considering to offer the backend package of this repo as an artifact on its own. It would be an artifact that bridges an OME-Zarr dataset to a Java class that represents it.
The class PyramidContents could be made to depend only on imglib2, which is okay for other Java projects like e.g. Icy, QuPath.
Then, the current Pyramidal5DImageData would be a wrapper to specifics for Fiji, exposing pixels as BDV's SourceAndConverter, ImageJ2's Dataset and ImageJ's ImagePlus.
Others (Icy, QuPath, ...) could wrap with their own "pixel data" classes. And they could depend only on this class without pulling the fiji stuff/deps (like, e.g., Dataset).
It would be worth considering to offer the
backendpackage of this repo as an artifact on its own. It would be an artifact that bridges an OME-Zarr dataset to a Java class that represents it.The class
PyramidContentscould be made to depend only on imglib2, which is okay for other Java projects like e.g. Icy, QuPath.Then, the current
Pyramidal5DImageDatawould be a wrapper to specifics for Fiji, exposing pixels as BDV's SourceAndConverter, ImageJ2's Dataset and ImageJ's ImagePlus.Others (Icy, QuPath, ...) could wrap with their own "pixel data" classes. And they could depend only on this class without pulling the fiji stuff/deps (like, e.g., Dataset).