search

CenterForDigitalHumanities / SpectralRTI_Toolkit

Process Spectral RTI Images in ImageJ
GNU General Public License v3.0
1 stars 0 forks source link

Required Pieces Packaging #60

Open thehabes opened 6 years ago

thehabes commented 6 years ago

Running around to download all the required packages is a bit of a pain. We should package all the required jars (in the repo) and all the required software (Kakadu, RTIViewer, RTIBuilder) together and offer as a zip file in the repository.

We could do the same with Fiji and put all the required plugins in the appropriate place in the plugins folder ahead of time and offer as a zip. We would need a Windows and a non windows version. The user would get the same experience as downloading and installing, but we could already have the jars required packaged in. The user could run the update so we don't have to keep it up to date.

The general theme here is try to organize the repo better so the user has less to track down and download, and package anything together that we can ahead of time for users.

Domhnall101 commented 6 years ago

This asks the question about rights to use the fitter and compressor. Can we bundle them or do we have to provide documentation to link to them? Kakadu looks to have gone to a pay model.

thanneken commented 6 years ago

http://kakadusoftware.com/downloads/

You are free to trial these executables and even to re-distribute them, so long as such use or re-distribution is accompanied with this copyright notice and is not for commercial gain. Note: Binaries can only be used for non-commercial purposes.

The Kakadu binaries are free for the level of use we need.

I see more value in making the dependencies for other plugins within ImageJ work smoothly (seems doable). Saving work to download and install other programs is nice, if it is easy to do.

thehabes commented 5 years ago

We will have a look at these as we combine repos.

thehabes commented 5 years ago

I organized under folders. I am not sure we can package where it is a download, double click and done. What we would need for that is a version of imageJ in this repo with all the required pieces already in it, or to write a platform independent install script that moved everything together for you automatically once you downloaded it on your machine.

What should be offered, properly aggregated and labeled, at the root is

Creating an installer would mean picking the package maker and doing the settings. https://stackoverflow.com/questions/14685149/creating-an-installer-for-java-desktop-application. This may be out of scope for the CDH at this point but is definitely something that could be looked at in the next round or informally in-between.