Blog

A first working version of the ImageJ2 Updater was integrated into the code base. This is an important step: the Updater can connect not only to the primary ImageJ2 update site, but to any number of update sites a user might configure. Likewise, advanced users may wish to set up their own update sites, which only requires a web site with either direct file access, or SSH/SFTP access (SFTP support was contributed by Jarek Sacha).

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

This is an experiment. I will write this blog entry in a completely non-technical style, just for fun. Hope you enjoy it, if not: stop reading.

The little sound flashes of the heater which it always makes when it automatically turns off because the desired temperature has been reached woke me up. Moving pictures play on the wall, painted by the blinds as a painter, painting with the bright rays of the early Sunday morning sun as paint.

My eyes slowly adjust to the beginnings of my day as the thoughts wander in from the far land of dreams.

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.

ImageJA started out as a two-pronged project:

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.