User Story #452 (closed)
Opened 18 years ago
Closed 15 years ago
Removal of RGB Rendering Model
| Reported by: | cxallan | Owned by: | cxallan |
|---|---|---|---|
| Priority: | minor | Milestone: | OMERO-Beta4 |
| Component: | Bin-Services | Keywords: | n.a. |
| Cc: | jburel, jamoore | Story Points: | n.a. |
| Sprint: | n.a. | Importance: | n.a. |
| Total Remaining Time: | n.a. | Estimated Remaining Time: | n.a. |
Description
The RGB rendering model is a holdover from the client side rendering engine that doesn't fit well with the colour choices one would like to make. Having to flip the rendering model when one wants to assign channel 0 to blue, channel 1 to green and channel 2 to blue explicitly is less than ideal.
The real benefit this has is allowing an optimization to be enabled when you don't have colour component overlap in the user's colour choices. The rendering engine should be smart enough to enable this optimization based on the user's colour choices and not have to have the rendering model flipped by the API user.
In short, the model should be removed and the optimization enabled intelligently by the rendering engine.
Change History (6)
comment:1 Changed 18 years ago by cxallan
- Component changed from General to Bin-Services
comment:2 Changed 17 years ago by cxallan
- Keywords iteration3 added
- Status changed from new to assigned
- Version 3.0-Beta1 deleted
comment:3 Changed 17 years ago by cxallan
- Milestone changed from 3.0-Beta2 to 3.0-Beta3
comment:4 Changed 16 years ago by cxallan
- Keywords iteration3 removed
comment:5 Changed 16 years ago by cxallan
- Milestone changed from 3.0-Beta3 to 3.0-Beta4
Just hasn't been a necessity to remove this in milestone:3.0-Beta3, moving to milestone:3.0-Beta4.
comment:6 Changed 15 years ago by cxallan
- Resolution set to fixed
- Status changed from assigned to closed
Removed.
Largely resolved as part of r1574, the actual removal of the extra code will come in milestone:3.0-Beta3.