Ticket #47 (closed feature: wontfix)
Opened 2010-03-01T20:48:43-06:00
Last modified 2013-06-07T15:37:54-05:00
Explore deployment/integration via Java Advanced Imaging
| Reported by: | curtis | Owned by: | curtis |
|---|---|---|---|
| Priority: | major | Milestone: |
|
| Component: | Core | Version: | |
| Severity: | non-issue | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | #9, #1001, #1912 |
Description
Java Advanced Imaging is a Java extension API that provides an integrated way to code image processing and I/O routines.
Since ImageJ and Bio-Formats specifically provide such functionality, it would make sense to leverage the JAI framework wherever applicable, and could even assist with the API design for our eventual OpenCL support.
Change History
comment:1 Changed 2010-03-30T15:41:16-05:00 by curtis
- Milestone changed from imagej-3.0 to imagej-2.0-beta
comment:2 Changed 2011-02-23T14:20:36-06:00 by curtis
- Status changed from new to closed
- Resolution set to wontfix
We now have a pretty solid workflow/plugin extensibility framework, which does not rely on JAI. Future potential for interoperability is still there, but I am closing this ticket.
comment:6 Changed 2013-06-07T15:37:54-05:00 by curtis
- Blocking 9 added
(In #9) This ticket is really about improving the infrastructure if I/O for ImageJ2. With SCIFIO, we have now done that. The 2.0.0-beta-7 release is using SCIFIO 0.1.0—File Open and File Save are now extensible—so this ticket is complete.
Remaining tickets about improving the existing I/O mechanism have been migrated to ticket #1920.
I am upgrading the milestone for this investigation because use of JAI could substantially inform our design.
Relevant links include: