These are chat archives for fiji/fiji

2nd
Feb 2016
Curtis Rueden
@ctrueden
Feb 02 2016 15:26
Ulrik Günther
@skalarproduktraum
Feb 02 2016 15:41
@ctrueden: we had this report yesterday: ClearVolume/ClearVolume#43 - do you have any clue what it could be related to? from my understanding the Fraction class is and has been for a long time in imglib2...
Curtis Rueden
@ctrueden
Feb 02 2016 15:45
@skalarproduktraum Sure, that is because the version of imglib2 on the class-path is too old. The Fraction class is relatively new (within the last 1-2 years?).
Or maybe imglib2 is not on the class-path at all...
Ulrik Günther
@skalarproduktraum
Feb 02 2016 15:47
but imglib2 ships with fiji, doesn’t it?
and we states that he has just updated his fiji install
Curtis Rueden
@ctrueden
Feb 02 2016 15:48
I wrote on the bug report, to give advice on how to troubleshoot his installation.
Ulrik Günther
@skalarproduktraum
Feb 02 2016 15:48
thanks :)
Curtis Rueden
@ctrueden
Feb 02 2016 15:48
No problem!
Michael Doube
@mdoube
Feb 02 2016 21:29
@ctrueden: thanks for the hint. Unfortunately I can't run that code in ImageJ1 because it requires importing classes that I can expect won't be there. This might just be one to solve in documentation.
Curtis Rueden
@ctrueden
Feb 02 2016 21:30
@mdoube Sorry, I don't understand the problem.
Are you trying to keep BoneJ2 compatible with vanilla ImageJ 1.x?
Michael Doube
@mdoube
Feb 02 2016 21:33
No - I'm trying to warn users of BoneJ1 that it won't work any more in too-new versions of ImageJ2. Lately all the 3D meshing API got moved out of the 3D Viewer which breaks quite a lot of stuff for BoneJ1. Since we're moving into the future with BoneJ2, I felt it would be better to let people know that their BoneJ1 will hold them back and give a reason for why things suddenly stopped working.
There are no BoneJ2 users yet - I don't expect any for a year or more.
Curtis Rueden
@ctrueden
Feb 02 2016 21:34
The 3D meshing stuff disappeared from the 3D Viewer? It didn't yet on master, did it?
I thought that was just @kephale 's work on a topic branch...
Michael Doube
@mdoube
Feb 02 2016 21:34
Let me check - might just be what @rimadoma reported from his build environment
Kyle I S Harrington
@kephale
Feb 02 2016 21:34
I didnt do it!
Michael Doube
@mdoube
Feb 02 2016 21:35
OK - before I cast anymore aspersions / throw stones in glass houses, I'l go check my facts
Kyle I S Harrington
@kephale
Feb 02 2016 21:35
:-D
Curtis Rueden
@ctrueden
Feb 02 2016 21:36
We certainly do not intend to break BoneJ1 with any ImageJ2 updates. It's just that we don't have any automated tests for that, so it's hard to always avoid doing so. But if stuff breaks, please complain and we'll do what we can to undo the damage.
Kyle I S Harrington
@kephale
Feb 02 2016 21:36
And actually within that topic branch, I was keeping the meshing stuff in 3D viewer as well, just for backwards compatibility for now, and just adding extra stuff for using ImageJ-ops meshing
Curtis Rueden
@ctrueden
Feb 02 2016 21:36
/me nods
ctrueden @ctrueden nods again
Curtis Rueden
@ctrueden
Feb 02 2016 21:36
Aww, no /me with edits, eh.
Michael Doube
@mdoube
Feb 02 2016 21:47
OK - I take it back. BoneJ 1.4.1 works fine in a just-updated Fiji. Not sure what it was I saw that broke it (or made me think it would soon be broken). Until BoneJ2 is out, it would be great to leave the 3D Viewer's API intact (at least from our selfish perspective). As for automated testing @ctrueden , that would be a great topic of discussion for you and @rimadoma later this month. We'll look to add testing for BoneJ2, synchronised as far as possible with the rest of the ecosystem, but leave BoneJ1 in old-school-manual-testing land to encourage user migration & to focus our resources on BoneJ2 development. I kind of expect BoneJ1 to get gradually broken by developments to ImageJ2 - at some point it will be unusable in contemporary ImageJ.
Curtis Rueden
@ctrueden
Feb 02 2016 22:14
Sounds great @mdoube. Except for the "gradually broken" part—but time will tell. You're probably right.