Task #3786 (new)
Opened 9 years ago
Last modified 3 years ago
Rendering Def part of the model?
| Reported by: | jburel | Owned by: | jburel |
|---|---|---|---|
| Priority: | major | Milestone: | Unscheduled |
| Component: | Model | Version: | 4.4.9 |
| Keywords: | schema | Cc: | jamoore, rleigh |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
To support Big image, we will need to adjust the rendering settings.
- viewport
- zoom level
- other?
Change History (20)
comment:1 Changed 8 years ago by jburel
- Milestone changed from OMERO-Beta4.3 to Unscheduled
comment:2 Changed 8 years ago by jmoore
Referencing ticket #3533 has changed sprint.
comment:3 Changed 7 years ago by jburel
Do we want to consider/discuss that ticket for 4.4? Probably only part of the OMERO model.
It will be similar to ROI. so maybe we can close it. Discussions about common rendering started in Dresden
comment:4 Changed 7 years ago by jmoore
J-M: I would think we should at least discuss it, and rather soon, for inclusion in the 4.4 DB upgrades.
comment:5 Changed 7 years ago by jburel
Having ability to save information for big images will be useful but we probably need more feedback/usage.
Moving the RenderingDef to the OME model now is probably not the right time, especially if we start using the code from Edi group.
comment:6 Changed 7 years ago by jmoore
Makes sense, J-M, but if we know that there's anything we will need regardless of new server implementations, we should likely make those incremental changes now, since we intend to have this DB version around for some time.
comment:7 Changed 7 years ago by jburel
In that case the 2 things for big images I can see to avoid numerous calls to the server:
- level
- viewer port bounds
This will also improve the synchronization between the 2 clients.
comment:8 Changed 7 years ago by jmoore
- Milestone changed from Unscheduled to OMERO-Beta4.4
- Owner set to ajpatterson
Andrew, can you get this scheduled/linked into the rest the schema upgrade tickets, etc?
comment:9 Changed 7 years ago by jburel
Adding the new value to the rendering Def in DB ok, modeling probably not especially if we decide to use the work done by Edi.
comment:10 Changed 7 years ago by jmoore
Except that we are trying to minimize differences, right? Is this something that would go in omero.xsd?
comment:11 Changed 7 years ago by jburel
omero ok I understood you wanted to promote it to the top level.
comment:12 Changed 7 years ago by jburel
- Cc dzmacdonald removed
- Milestone changed from OMERO-Beta4.4 to OMERO-Beta4.5
We need discussion with various groups: imageJ2, knime, imglib etc. so we have one common place. Pushing to 4.5
comment:13 Changed 7 years ago by ajpatterson
- Keywords schema-2012-06 hold added
On hold pending reintegration code changes from schema-2012-06 branch
comment:14 Changed 7 years ago by ajpatterson
- Milestone changed from OMERO-5 to Future
comment:15 Changed 7 years ago by ajpatterson
- Owner ajpatterson deleted
comment:16 Changed 6 years ago by jburel
- Cc rleigh added; cxallan ajpatterson removed
- Milestone changed from Future to 5.0.0
- Owner set to ajpatterson
- Version set to 4.4.9
comment:17 Changed 6 years ago by jburel
- Keywords schema-2012-06 hold removed
comment:18 Changed 6 years ago by ajpatterson
- Keywords schema added
If "schema-2012-06" keyword needs removed it should be replaced with "schema"
comment:19 Changed 4 years ago by ajpatterson
- Owner changed from ajpatterson to jburel
comment:20 Changed 3 years ago by jamoore
- Milestone changed from 5.x to Unscheduled
Pushing this ticket, we will need to feedback first.