search

mobie / mobie-viewer-fiji

BSD 2-Clause "Simplified" License
33 stars 13 forks source link

Can we get rid of imagej-utils dependency? #204

Open tischi opened 3 years ago

tischi commented 3 years ago

@K-Meech @constantinpape

Before submission, I would like to clean up quite a bit of the image segments visualization logic.

The most fun way of doing this would involve a white-board such that we can draw how all the parts communicate with each other.

constantinpape commented 3 years ago

Before submission, I would like to clean up quite a bit of the image segments visualization logic.

Sounds good.

The most fun way of doing this would involve a white-board such that we can draw how all the parts communicate with each other.

We could try to find a room at EMBL on the 23rd to do that in a socially distanced way (I guess @K-Meech will not be able to join in person though, but should be fine to do that partially over zoom.)

K-Meech commented 3 years ago

Sounds good! But yes - I'm still in the UK unfortunately... Can join via zoom though :)

tischi commented 3 years ago

I think also one thing to consider is to separate the code into mobie-core and a mobie-fiji-plugin.

Then we could rewrite everything that currently is a mess in imagej-utils into improved versions in mobie-core and we (@K-Meech and I) could depend on mobie-core with some of our other projects. The point would be that mobie-core would not add anything to the Fiji user interface.

Another thing to check is whether mobie-core or (better) only mobie-fiji-plugin could depend on https://github.com/bigdataviewer/bigdataviewer-playground, which contains a collection of useful bdv related functionalities.

In general, thinking about dependencies would be important in order not too have too much work with the maintenance of the whole project.

constantinpape commented 3 years ago

I am not sure if this is still relevant, but given that there are a lot of small follow up issues that seem to be related to this one I am gonna leave it open for now.