User Story #188 (closed)
Opened 13 years ago
Closed 13 years ago
Rendering Engine Usage Metadata Methods
| Reported by: | cxallan | Owned by: | cxallan |
|---|---|---|---|
| Priority: | minor | Milestone: | 3.0-M3 |
| Component: | General | Keywords: | iteration4 |
| Cc: | jburel | Story Points: | n.a. |
| Sprint: | n.a. | Importance: | n.a. |
| Total Remaining Time: | n.a. | Estimated Remaining Time: | n.a. |
Description
Metadata methods are needed in the rendering engine API to retrieve:
- All available Rendering Models
- All available Families
- The active pixels set
Change History (7)
comment:1 Changed 13 years ago by cxallan
- Resolution set to fixed
- Status changed from new to closed
comment:2 Changed 13 years ago by anonymous
- Resolution fixed deleted
- Status changed from closed to reopened
Reopened ticket b/c we will need extra methods for codomain transformations
comment:3 Changed 13 years ago by cxallan
Will need to deal with #188 when we deal with Jean-Marie's codomain transformations.
comment:4 Changed 13 years ago by cxallan
- Keywords iteration4 removed
- Milestone changed from 3.0-M2 to 3.0-M3
- Version changed from 3.0-M2 to 3.0-M3
comment:5 Changed 13 years ago by cxallan
- Keywords iteration4 added
Assigning this for when we deal with the metadata.
comment:6 Changed 13 years ago by cxallan
Closing with r922.
comment:7 Changed 13 years ago by cxallan
- Resolution set to fixed
- Status changed from reopened to closed
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Closing with r734. We've also got usage of the pixels service throughout to allow enumeration lookup instead of using OmeroContext to grab a query service.