NOTICE! This is a static HTML version of a legacy ImageJ Trac ticket.

The ImageJ project now uses GitHub Issues for issue tracking.

Please file all new issues there.

Ticket #551 (closed task: fixed)

Opened 2011-05-31T15:25:06-05:00

Last modified 2011-10-18T16:18:27-05:00

Improve legacy layer

Reported by: bdezonia Owned by: bdezonia
Priority: major Milestone: imagej2-b1-initial
Component: Legacy Compatibility Version:
Severity: serious Keywords:
Cc: Blocked By:


The legacy layer is now well fleshed out. Write more comprehensive tests for the ImageTranslators and the DatasetHarmonizer.

Change History

comment:1 Changed 2011-07-29T13:16:09-05:00 by bdezonia

  • Summary changed from Improve legacy layer unit tests to Improve legacy layer
  • Milestone changed from biweekly-2011: Jul-18 to Jul-29 to imagej-2.0-alpha5

Also refactor the legacy layer classes for simplification. Break out LegacyUtils into classes. Eliminate the DefaultTranslator class.

comment:2 Changed 2011-09-13T09:47:02-05:00 by bdezonia

  • Milestone changed from imagej-2.0-alpha5 to imagej-2.0-beta1

comment:3 Changed 2011-10-04T15:04:09-05:00 by bdezonia

The legacy layer translates between Displays and ImagePluses. Since the Display part is tied to the UI and the DisplayService we cannot really write test code for these classes. Once we define HeadlessUI classes this could be fixed.

comment:4 Changed 2011-10-18T16:18:27-05:00 by bdezonia

  • Status changed from new to closed
  • Resolution set to fixed

Refactored the legacy layer substantially. Two main commits were 3fe4fdddebdae6ba060f51438c32a9f9dbad322c and 12fbf9e6d030b790f6084869fffc9b66e8619813 with a few minor commits in between.

Since we cannot test the legacy code until headless ui is in place I will consider this ticket done and open another specifically aimed at testing.