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 #1005 (closed feature: wontfix)

Opened 2012-02-23T14:33:48-06:00

Last modified 2014-05-10T21:44:24-05:00

Interoperability between ImageJ and ICY

Reported by: curtis Owned by: curtis
Priority: major Milestone: imagej-2.0.0
Component: Other Version:
Severity: non-issue Keywords:
Cc: Blocked By:
Blocking: #1001

Description (last modified by curtis)

This is a blanket feature ticket representing desired interoperability between ImageJ2 and ICY. See blocking tickets for specifics.

Change History

comment:1 Changed 2012-02-23T14:34:16-06:00 by curtis

  • Description modified

comment:2 Changed 2014-05-10T21:44:24-05:00 by curtis

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

The ICY team  partipated in the Dec 2011 Dresden hackathon. Stephane Dallongeville looked into the possibility of supporting ImageJ2 modules within Icy. Not sure if the work has been pursued since then. It was  briefly discussed on the Icy forum, and for now the ball is in the Icy team's court. Some day we may have time and need to splice ImageJ2 module support into Icy, but probably not in the near future. Perhaps if/when ImageJ2 modules become more prevalent, Icy will gain support for them then.

Last edited 2014-05-10T21:44:49-05:00 by curtis