Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #10625 (new)

Opened 11 years ago

Last modified 8 years ago

Change settings big image

Reported by: jburel Owned by: jburel
Priority: major Milestone: Unscheduled
Component: General Version: OMERO-5.2.0
Keywords: n.a. Cc: ux@…, jamoore, cxallan
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.

Description

Big images are usually "RGB" images, we should turn off the ability to modify the rendering settings. The same should apply to any "graphics" images.

Change History (12)

comment:1 Changed 11 years ago by wmoore

Makes sense: The obvious question is how do we tell if an image was originally 'RGB'?

comment:2 Changed 11 years ago by rkferguson

What do you define "graphics" images as?

comment:3 Changed 11 years ago by jburel

jpeg, png, etc

comment:4 Changed 11 years ago by pwalczysko

I just discussed with Will. If this should be a total disabling on the Rendering setting pane (for which you have to press the icon in Insight or click Edit in Web), then I would say no. The reason is, that the adjustment of single colors post-acquisition is very important for example when you have hematoxylin & eosin stained cells and the slide ( = background) has a residue of these very blue and very red dyes (this is my first hand experience). You need to be able to render the red background out in order to see your cells better, to see the nuclei less blue, to get better contrast etc. Also the color cameras on the microscope might have a wrong color balance for whatever reason, which is another argument for being able to (for example) suppress the blue color against the red / green, because it was taken wrongly. These color images can very often have .jpeg format as they come off the microscope.

If this concerns only disabling of the channel toggles on the left side of the image, then yes, I do not see the reason for switching immediately the blue channel off or changing the color into black and white for such images. So yes, these channel buttons and the color picker could go - but still, I might be simply lacking some particular experience with a workflow for which this is important.

comment:5 Changed 11 years ago by jburel

will: from the format table

comment:6 Changed 11 years ago by rkferguson

What Petr says makes sense - and you might just want to change the tone for a publication or PPT slide etc.

comment:7 follow-up: Changed 11 years ago by jburel

If we are okay with changes described in #10626 i.e. bird eye view image not been updated then we can investigate further about what to turn on/off.

comment:8 Changed 11 years ago by wmoore

So, agreed so far that for certain formats (jpeg, png, svs? etc) in the main image viewer we hide the channel toggle buttons and grey/colour button to the left of the image, but don't change the ability to open the rendering panel to the right. NB: the grey/colour toggle is not in the right panel, so maybe we shouldn't hide this just in case?

comment:9 in reply to: ↑ 7 Changed 11 years ago by pwalczysko

Replying to jburel:

If we are okay with changes described in #10626 i.e. bird eye view image not been updated then we can investigate further about what to turn on/off.

I think that what is described in #10626 is acceptable.

comment:10 Changed 8 years ago by jamoore

  • Milestone changed from 5.x to Unscheduled
  • Version set to OMERO-5.2.0

comment:11 Changed 8 years ago by jamoore

Referencing ticket #7917 has changed sprint.

comment:12 Changed 8 years ago by jamoore

Referencing ticket #7917 has changed sprint.

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

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.68242 sec.)

We're Hiring!