User Story #8533 (closed)
Opened 7 years ago
Last modified 7 years ago
Legacy Bio-Formats Component
| Reported by: | mhiner-x | Owned by: | mhiner-x |
|---|---|---|---|
| Priority: | critical | Milestone: | Unscheduled |
| Component: | Bio-Formats | Keywords: | n.a. |
| Cc: | jamoore, mlinkert, crueden-x | Story Points: | n.a. |
| Sprint: | n.a. | Importance: | n.a. |
| Total Remaining Time: | n.a. | Estimated Remaining Time: | n.a. |
Description
A new Legacy Bio-Formats component is necessary to preserve backwards compatibility for the old loci.formats classes with the changing dependency structure implied by SCIFIO.
With a software stack that puts SCIFIO at the bottom, Bio-Formats depending on SCIFIO, and OME-XML at the top, the legacy Bio-Formats classes need to be above OME-XML as they have dependencies on every component in the stack (open formats defer down to the SCIFIO layer, proprietary formats to the Bio-Formats layer, and fundamental classes such as the IFormatReader/Writer require the OME-XML layer).
The classes in this legacy layer will be either empty extensions of their corresponding classes or will have the same signatures but defer to their analogs.
The end result is the preservation of the loci.formats package hierarchy to allow legacy code to continue to run without modification (although this new Bio-Formats Legacy jar will be required)
Change History (2)
comment:1 Changed 7 years ago by agilo
- Status changed from new to accepted
comment:2 Changed 7 years ago by mhiner-x
When this task is complete, our development workflow should be able to change. Instead of developing SCIFIO in a vacuum (on its own branch) which will constantly be struggling to keep up with the develop branch, we should be able to make SCIFIO a living part of develop immediately.
This will allow gradual conversion to SCIFIO-style readers.
Updated status, related task in progress