Task #3786 (new)

Opened 2 years ago

Last modified 4 months ago

Rendering Def part of the model?

Reported by: jburel Owned by:
Priority: major Milestone: Future
Component: Model Keywords: schema-2012-06, hold
Cc: jamoore, cxallan, ajpatterson Remaining Time: n.a.
Sprint: n.a. Resources: n.a.
References: n.a. Referenced By: n.a.

Description

To support Big image, we will need to adjust the rendering settings.

  • viewport
  • zoom level
  • other?

References

Change History

comment:1 Changed 2 years ago by jburel

  • Milestone changed from OMERO-Beta4.3 to Unscheduled

Pushing this ticket, we will need to feedback first.

comment:2 Changed 2 years ago by jmoore

Referencing ticket #3533 has changed sprint.

comment:3 Changed 16 months 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 15 months 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 15 months 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 15 months 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 15 months 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 15 months ago by jmoore

  • Owner set to ajpatterson
  • Milestone changed from Unscheduled to OMERO-Beta4.4

Andrew, can you get this scheduled/linked into the rest the schema upgrade tickets, etc?

comment:9 Changed 15 months 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 15 months ago by jmoore

Except that we are trying to minimize differences, right? Is this something that would go in omero.xsd?

comment:11 Changed 15 months ago by jburel

omero ok I understood you wanted to promote it to the top level.

comment:12 Changed 12 months 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 4 months ago by ajpatterson

  • Keywords schema-2012-06, hold added

On hold pending reintegration code changes from schema-2012-06 branch

comment:14 Changed 4 months ago by ajpatterson

  • Milestone changed from OMERO-5 to Future

comment:15 Changed 4 months ago by ajpatterson

  • Owner ajpatterson deleted
Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.2-PRO © 2008-2010 agile42 all rights reserved (this page was served in: 2.306923 sec.)

We're Hiring!