Currently, we rely on a wrapper plugin to handle the bridge between imagej.js and itk-vtk-viewer. A better way to do this is to register a service (see the new api.registerService api) directly from the viewer, say, visualization service, and ImageJ.JS and other site with imjoy-core can then discover and consume the visualization service.
Cool idea regarding the service! A refined idea of how the API would work nicely will come as we address #348 and we make more lazy-zarr backend examples.
I just shipped itk-vtk-viewer in ImageJ.JS, see it in action: https://ij.imjoy.io
Would be nice to have https://github.com/Kitware/itk-vtk-viewer/issues/348 and https://github.com/Kitware/itk-vtk-viewer/issues/347 solved so I can hide the UI control by default and set the origin to the top-left corner (same as imagej).
Currently, we rely on a wrapper plugin to handle the bridge between imagej.js and itk-vtk-viewer. A better way to do this is to register a service (see the new
api.registerService
api) directly from the viewer, say,visualization
service, and ImageJ.JS and other site with imjoy-core can then discover and consume the visualization service.