curtis's blog

As mentioned on the mailing list, we have updated our web resources to be more unified under the imagej.net domain name:

When we launched the ImageJ2 project, we began by writing many unit tests to protect ImageJ 1.x from regression bugs. At this writing, there are unit tests in place for 50 core IJ1 classes, intended to detect bugs introduced during ImageJ development. These tests are located in the ij1-tests directory.

The following is a quick technical update on some work I am doing on ImageJ2's display hierarchy. It will mostly be of interest to other IJ2 developers, but I am posting here to give the community a rough idea of where we are going with the display code.

Today we are releasing a fifth alpha of ImageJ2, version 2.0.0-alpha5. This is an "alpha"-quality release, meaning the code is not finished, nor is the design fully stabilized. We are releasing it for early community feedback, and to demonstrate project directions and progress.

Unfortunately, the code is still not far enough along to be called "beta," as we are still working through some remaining design issues as well as strengthening compatibility with ImageJ v1.x. See the Downloads page for our revised timetable.

The following is a status update as of 2 August 2011. Yesterday we released ImageJ 2.0.0-alpha4, and we have made great progress in many areas since the last major status update in December.

Today we are releasing a fourth alpha of ImageJ2, version 2.0.0-alpha4. This is an "alpha"-quality release, meaning the code is not finished, nor is the design fully stabilized. We are releasing it for early community feedback, and to demonstrate project directions and progress.

Unfortunately, the code is still not far enough along to be called "beta," as we are still working through some remaining design issues as well as strengthening compatibility with ImageJ v1.x. See the Downloads page for our revised timetable.

With ImageJ1, there is a singleton instance of the program, accessible via IJ.getInstance(). With ImageJ2 we want to provide a mechanism for managing multiple ImageJ "application contexts." At the moment, ImageJ2 is also still a singleton, but we recently did some work to pave the way for multiple ImageJ applications running simultaneously.

ImageJ2 has a flexible "extensibility framework" for managing plugins and their cousins, modules. Lately we have been making big improvements that are too numerous to mention here. But I wanted to make note of some of the progress that we made within the past couple of days. Be warned: it is very technical and will likely only be of interest to other ImageJ2 developers.

According to our roadmap for ImageJ2, we should be releasing the first beta of ImageJ v2.0.0 today. Unfortunately, the program is still not ready to be released as a beta. Thus, we are pushing back the beta1 release to some time in July, with a deadline of July 31st.

Today we are releasing the third alpha of ImageJ2, version 2.0.0-alpha3. This is an "alpha"-quality release, meaning the code is not finished, nor is the design fully stabilized. We are releasing it for early community feedback, and to demonstrate project directions and progress.