Open ctrueden opened 1 year ago
My only minor complaint is that it is in a Scala dialect.
@mkitti it is not a dialect of Scala. It is a standard mainstream Scala, compiled to a native binary.
@ctrueden
The question is just whether all needed existing features can successfully be wrapped into the new codebase, but I suspect the answer is yes.
To be more precise, the question to answer is: which existing features are actually needed going forward?
The just released version 0.2.0 added some key features needed for drop-in replacement, for instance, now it supports installing Fiji in macOS Application folder. Currantly supported features are described in Readme/Features. Next version will add ImageJ1 and ImageJ.cfg support.
It will be helpful to have some documentations what are the features of the current launcher that are important to be preserved going forward.
The ijp-imagej-launcher project by @jpsacha is written in Scala, compiles to a simple native executable, and is much less code than this project. It does not yet recapitulate everything the current ImageJ Launcher can do, but could probably be made to do so, and would be vastly more maintainable than the current codebase.
Here is what @jpsacha wrote to me via email about the motivation for ijp-imagej-launcher:
The question is just whether all needed existing features can successfully be wrapped into the new codebase, but I suspect the answer is yes.